Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Topics - namida

Pages: 1 2 [3] 4 5 ... 57
31
If multiple lemmings exit on the same frame, and this causes the saved amount to jump from a value below the requirement to one above it (without ever hitting the requirement exactly), the level does not get marked as completed. (A previous theory about the cause of this turned out to be incorrect.)

32
This is a purely visual bug; the underlying physics work correctly. When a lemming uses a rope slide, its sprite is displayed lower than it should be.

Complicating this is that the offset is not always the same. It's usually about two slabs height too low, but eg. in Mayhem 64 "Ski Jump" it's only about one slab.

33
On the included portal object in namida_systemtest, the result is the receive point being 1 pixel further to the right than it should be. (Workaround for this in the meantime is to move all portals where this positioning is critical, eg. portals that receive lemmings who are climbing / sliding, one pixel to the left.)

Untested how flipped portals are affected and what the exact cause / impacts are, beyond the observed effects on the sample object.

34
Can be seen at around 51:50 in Ryemanni's video here: https://www.youtube.com/watch?v=e1Zl9qzrYeI

Basically, the lemming should not turn around. His first course of action if suitable should be to attempt to ascend the wall (if either it's only one slab high, or if he is a climber), otherwise, he should turn in accordance with the block's direction. He should only turn around in this case if the wall is not a deflector and not ascendable.

Related to this, a miner who is also a climber and hits a wrong-one-way-wall (maybe also steel?) turns around instead of climbing it.

35
Loap / [BUG] Hotkeys get "stuck" when file selector opens
« on: March 10, 2022, 06:19:18 PM »
Steps to reproduce (one example):
1. Assign "Load Replay" and a move camera function to the same key
2. Load a replay on the preview screen via this hotkey
3. Go into gameplay
4. Notice how the camera moves as if you were still holding the key

Quote
Okay so, this one seems to be something pretty low-level in how the framework and the file-select dialog interact with each other, so I'm not sure that I can fix it. Putting them on different hotkeys should help, of course; beyond that, I likely need to find a better cross-platform solution to open a file dialog, or failing that, write platform-specific code each for Windows and Linux here to handle it properly without interfering with keyboard input. This is likely to become one of those minor "stuck" bugs that doesn't get fixed for a long time, unfortunately.

36
Loap / Coarse-grained Spawn Interval
« on: February 14, 2022, 08:14:38 AM »
Edit Simon: Split from Simon blogs, committees and spawn intervals

Quote
VSI had nonzero benefit and still sparks debate.

As you'll recall, I gave thought to this for NeoLemmix at one point. I wasn't very keen on an outright cull; I was a lot more keen on the idea of making it much less fine-grained; having a smaller number of possible values (with a larger difference in spawn interval between them).

With Loap, I have gone for such an approach right from the start. Instead of 1 to 99, Loap's spawn rate (I'm using this term internally, though I suspect people will likely continue using "release rate" in most discussions, to differentiate it) ranges from 0 to 9. A Loap SR n is equivalent to an L3D release rate of n9 (eg. 9 is equivalent to 99, 8 to 89, etc). It's now confirmed that all official levels are solvable (including Winterland); some custom levels have issues, one of which is due to this (not due to the coarseness, but rather due to that Loap's minimum is equivalent to L3D's 9, while in L3D the level in question has an L3D RR of 1, and the difference is solution-breaking).

37
Loap / Linux build?
« on: February 12, 2022, 08:39:32 AM »
Is there anyone who'd be interested in me providing Linux builds during this early test-build phase? Note that I intend to, if possible, release Linux builds once it's time to go stable either way . This is purely about during the current phase of development.

(Mac, on the other hand, I am going to rule out at least during the test phase.)

38
Closed Loap Bugs / Suggestions / Virtual Lemming / Highlight bugs
« on: February 07, 2022, 06:17:35 PM »
(Note that at the time of creating this topic, these two features are not supported in the latest release build, but are supported in the latest commits on Bitbucket.)

Applicable to both
- The Turner skill cannot be assigned
- Skill icons don't do the "animate once" thing like they do in L3D

Exclusive to Highlight
Currently none

Exclusive to Virtual Lemming
- Camera immediately snaps when lemming turns around instead of a gradual rotation like in L3D
- Camera direction doesn't change for Blockers / Turners
- Lemmings in front of the VL camera, but behind or on the VL lemming's position (including the VL lemming himself) will be picked up by the mouse
- Other lemmings may disappear or flicker when in Virtual Lemming mode, usually only if the camera is rotated
- The shrugger ? icon is not visible for the VL lemming in Virtual Lemming mode

39
Closed Loap Bugs / Suggestions / DireKrow's missing feature list
« on: February 07, 2022, 01:00:05 AM »
Copy-paste from Discord. Updated as I work on things with strikeouts / new additions.

Quote
Main things L3D has which Loap currently doesn't:
- Virtual Lemming. (added in commit 2504296 / for V0.0.14.0)
- Hilight Lemming. (added in commit 7f92b4c / for V0.0.14.0)
- Proximity-based sfx volume. (added in commit 71cdae5 / for V0.0.14.0)
- Solid camera physics. (added over several commits, can be considered complete as of 5b44093 / for V0.0.15.0)
- Display a lemming's assigned skills on hover. (added in commit 1ec80a3 / for V0.0.15.0)
- Automatic level exiting. (added in commit 7f9334b / for V0.0.15.0)
- Visible cameras. (added in commit 7df92ec / for V0.0.15.0)
- Hatch opening animation / sound. (added over several commits, merged in a6a7460 / for V0.0.18.0)
- Main menu. (added in commit 321c524 / for V0.0.18.0)
- Automatic replay saving. (added in commit b2d8bb3 / for V0.0.16.0)
- Options menu. (added over several commits, completed in 687ffb2 / for V0.0.22.0)
- Minimap. (implemented over several commits in a seperate branch, merged in 1e33ecc / for V0.0.21.0)
- Level select, including records. (virtually complete in V0.0.23.0; record display will be included in V0.0.24.0)
- Hotkeys menu.

For options, chiefly I'd say display and render resolutions, fs/windowed, vsync/framelimiter, music/sound vol, key & mouse rebinding, camera sensitivity, cursor lock on drag, cursor trap in window are the main things you'd want for this in v1.0.

NL features that are not in L3D but are desirable in Loap:
- Save state and load state.
- (Mass) replay check. (implemented in a side branch, merged in commit f4f9261 / for V0.0.23.0)
- Button to hold to assign to walkers only. (implemented in commit 5a8100c / for V0.0.23.0)
- Go to next shrugger button. (implemented in commit 1e4fd59 / for V0.0.24.0)
- Hilighting currently selected lemming on hover. (not going to happen)
- Changing climber/floater/etc's color. (not going to happen)
- Clear physics mode equivalent.
- Insert mode and replay editor.

Then there's the editor, if you choose to make one.

40
Closed Loap Bugs / Suggestions / [BUG] Basher doesn't stop at slope
« on: February 06, 2022, 10:40:30 PM »
In L3D a basher will stop if there isn't a wall in front of him when he reaches the edge of a block. In Loap, he will currently bash even for a slope in this case - which L3D only allows when the basher is first assigned.

In particular, this prevents the (presumably) intended solution to Tricky 29 "Land Ahoy" from working (though the level can be solved via backroutes).

41
Haven't tested if this also happens with teleporters and rope slides. Not tested, but my hunch is this will not affect blockers.

EDIT: Confirmed for rope slides too.

42
In L3D, you can see other cameras as actual visible objects.

While an option to turn this off might be desirable, Loap should at least allow showing them.

43
Screenshots illustrate better than words do for this one.

44
To reproduce:
1. Let a builder build at least two steps
2. Assign a basher to a lemming who is standing on one step, and on the next frame will move upwards onto the next step

The result is that the lemming will have the basher animation for 1 frame, before falling through the bridge (without damaging it).

45
Closed Loap Bugs / Suggestions / Builder issues at top of slope
« on: February 02, 2022, 06:23:25 PM »
Seems to be that the "go down the slope" is overriding "step up onto the brick" instead of the other way around.

Pages: 1 2 [3] 4 5 ... 57