-
Posts
8404 -
Joined
-
Last visited
-
Days Won
105
Posts posted by AluminumHaste
-
-
Turn off bloom?
-
That's the new version, it used to be a real key would fall out.
Was causing issues where players would lose it and couldn't find it.
I don't remember how they did that originally.
-
On 9/15/2023 at 2:24 PM, grodenglaive said:
I tried to add a custom collider to a pot so you could, for example, hide a key in it that would fall out if the player tipped the pot upside down. This doesn't seem possible - any collider that isn't a single solid polygon gives me an error on map start.
For example, something like this doesn't work:
Is this just a limitation of the engine or is there a way to do it? It's not super important, I just thought it would be cool to do.
This was done in the mission Tears of Saint Lucia, where you have to shoot a vase with a key in it off a ledge.
It's right at the start of the mission, so go see how that was done.-
1
-
-
17 minutes ago, wesp5 said:
I get a black screen with the latest executable. Do we need the last release candidate for this to work? I am still on 2.11...
Yeah, you need to be on 2.12 beta for this to work.
-
16 hours ago, Daft Mugi said:
@AluminumHaste Could you please make a new build? (Should be the last one.)
I've updated the patch to fix a bug when auto-search bodies is enabled and delay is 0, and I removed the "tdm_frobhold_drag_body_behavior" cvar.
After talking with a player on Discord, I changed the default delay to 200ms. Seems like that will also work well with your preference of 250ms.
Pros of 200ms:
- Dragging a body doesn't feel sluggish.
- Putting out a candle is pretty fast.
Cons of 200ms:
- New players might make a mistake (at first or without some practice). But will probably be ok.
I think using 200ms, which I know is good, is better than going with my original assumption. If players have trouble during dev or beta, it can be changed back to 300ms. Better that I go with data than assumptions.
New Binaries: https://drive.google.com/file/d/1L0GmR5Jn79mGDWXNLzP4bsGzRo-Wnp0j/view?usp=sharing
-
2
-
Just put kids to bed, doing laundry, hopefully in a bit
-
1
-
-
I usually prefer 250ms, 1/4 of a second, but some players with slower reflexes might have a harder time. Just try it as is to see what people think
-
1
-
-
Yeah, this is a good change.
-
1
-
-
6 minutes ago, Daft Mugi said:
After some feedback, I changed the candles and lantern behavior to pick up on frob and extinguish on long-press frob.
Candle holders without candles required a long-press frob to pick up. That didn't feel right.
Pros of this change:
- More consistent: frob always picks up items, candles, and bodies.
- Long-press acts like a special action: drag for bodies, extinguish for candles.
- Bonus: long-press frob to extinguish feels like pinching out a candle.
@AluminumHaste Could you please update the build again?
Done: https://drive.google.com/file/d/1L0GmR5Jn79mGDWXNLzP4bsGzRo-Wnp0j/view?usp=sharing
-
2
-
First time I've noticed it lol.
-
This is what I get (Still processing):
-
Look how comfortable she looks?
-
2 hours ago, Daft Mugi said:
I've never done that with limbs, just items. Do you regularly do that? Does anyone?
For example, you can't get bodies in places like this without pushing the held limbs away.
-
Just now, AluminumHaste said:
I can also drop the body with Use key.
I can also drop the body with Drop key
Also, when picking up and dropping bodies over and over again, it's supposed to flip the body over. Now it's flipping AND rotating the body 180 degrees
-
2 minutes ago, AluminumHaste said:
I can drop a body with Frob (Mouse2)
I can also drop the body with Use key.
-
5 minutes ago, Daft Mugi said:
That shouldn't be the case. I wonder if it is the right binary?
lol. No worries. So, are you saying I can remove the cvar?
I can drop a body with Frob (Mouse2)
-
Yeah it's fine
-
1
-
-
Ok......don't be mad but;........I tried a bit more with scrolling while holding down the button and it's fine.
-
21 minutes ago, Daft Mugi said:
I've updated the patch (same link as before):
https://gist.github.com/daftmugi/41d0324107e8734f364bb3e50ff00794Added "tdm_frobhold_drag_body_behavior" cvar:
"tdm_frobhold_drag_body_behavior", default:"1" Which drag body behavior? 1 --- on frob key up, drop body (limb). 0 --- on second frob, drop body (limb), TDM v2.11 (and prior) behavior.
Added drop body on second frob, while allowing frob on doors, switches, etc.
(Not thoroughly tested, but it seems to be working as intended.)Could you please update the build?
New Binary: https://drive.google.com/file/d/1L0GmR5Jn79mGDWXNLzP4bsGzRo-Wnp0j/view?usp=sharing
-
3
-
-
NM, I undid the previous patch and applied the new patch.
-
2
-
-
Weird, when I tried applying the patch, 2 items failed.
SysCvar.cpp and Player.cpp.
Says rejected patch hunks
-
Not sure lol
-
Yes, allll the time. Have you ever shoved a body under a table/bed/shelf to hide it? You can't really do it without scroll wheel.
It works with ANYTHING in the grabber.
-
3 minutes ago, Wellingtoncrab said:
I think personally I prefer this to requiring another input to stop dragging - at least in the usual loop of shouldering a body to move it roughly where it needs to go and then using manipulate to tuck it in.
The click and release made it very quick to move individual limbs.
But yeah like lots of these types of things a "toggle" mode should be an option
True, however, you can push limbs away from you, or pull them closer with the scroll wheel.
Doing that while holding down the right mouse button was very painful.
[Feature Proposal] New Lean for TDM 2.12
in The Dark Mod
Posted
I was about to but in the process of cleaning out the previous patches, I accidentally did a svn cleanup command with delete all unversioned files, without realizing I had done so on the Darkmod game directory, not the source code directory.
Now Tortoise SVN claims that all these files would go to the recycle bin, but it's empty. Can't recover these files either, tried with several recovery tools.
So all that work in progress stuff was lost, maps, textures, shaders, etc. All gone, last back up was....2014. All my fault, but this is too crushing, I'm done with this project for now sorry.