redleaf on 24/12/2019 at 11:25
Now that I've completely trained my hand to perform Alt+R rather than Alt+E in DromEd, it has stopped working. Alt+R does nothing and ALT+E brings me back to the starting point. The only posts I found here all say to use Alt+R to bring you back to the game where you left off. Is this the right place to post this problem? Is it a tech problem?
I can't find any change in any command files that might have caused this. :p
john9818a on 25/12/2019 at 23:52
Code:
; ALT-
bind_all_alt-F1 mono_debug
bind_edit_alt-b edit_command save_group
bind_edit_alt-c edit_command clear_world
bind_game_alt-e edit_mode
bind_all_alt-g game_mode ; go into proto game mode
bind_edit_alt-l edit_command load_file
bind_edit_alt-o edit_command edit_obj; ; Object editor
bind_edit_alt-p auto_portalize ; toggle portalizing after every edit
bind_all_alt-q foot_sounds
;bind_edit_alt-r reset_brush ; 0 all brush rotation
bind_edit_alt-s eval world_file edit_command save_mission %s
bind_edit_alt-t texture_pal ; texture palette
bind_edit_alt-v edit_command load_group
bind_edit_alt-SPACE quick_resynch ; synch all windows, rerender, desynch them
This is how my keybind.cfg looks in my installation. In my case I use alt-e to go back to edit mode. The alt-r line has a ; in front of it. If you reverse those and make your alt-r line look like this:
Code:
bind_game_alt-r edit_mode
;bind_edit_alt-e edit_mode
it should fix the problem.
redleaf on 29/12/2019 at 05:40
I don't have a keybind.cfg. I can make one. Should I have one? Should it have come with the latest NewDark or tool kit?
redleaf on 29/12/2019 at 05:44
I can get back into the editor no problem using alt+e. I want alt+r to also work and take me back into the game where I left off. Alt+e takes me back to where I first entered.
redleaf on 29/12/2019 at 05:48
Yikes. I don't even know what some of those commands mean.
john9818a on 29/12/2019 at 22:13
You might also look at user.bnd, and if you don't have that file then look at default.bnd.
btw the mods frown upon triple posting especially when they are all within an eight minute period. :) Its easy to edit your post if you have additional comments.
redleaf on 30/12/2019 at 15:52
Got it about the moderators. Understood and thank you. I will look at my bnd files. I just think it's odd that Alt+R worked well for me all along, then suddenly stopped working. I cannot imagine anything that would have caused those files to change.
redleaf on 2/1/2020 at 14:38
Okay, this is what those files say:
Default.bnd: game bind e+alt "run .\cmds\EditMode.cmd" ; return to edit mode
game bind r+alt "run .\cmds\EditModeAtPlr.cmd" ; return to edit mode at player
User.bnd: bind e+alt "run .\cmds\editmode.cmd"
bind r+alt "run .\cmds\editmodeatplr.cmd"
I checked those commands:
EditMode.cmd = unset editorcam_from_game
edit_mode
EditModeAtPlr.cmd = set editorcam_from_game
edit_mode
unset editorcam_from_game
Should they say anything different?
redleaf on 8/1/2020 at 11:28
I guess I must be asking stupid questions?
R Soul on 8/1/2020 at 22:06
It's more likely that no-one else has had this problem.
What could be happening is that some other keybind is overriding Alt+R, so search user.bnd to see if it's configured twice. I don't know if it's possible, but it could even be something like Shift+Alt+R for some other command.
I don't see the use of returning to the editor where you last entered game mode (the default for alt+E) with those .cmd files. I had the exact same .cmd file setup and default.bnd as you, but I had an older user.bnd so for me Alt+E was just running the edit_mode command (and I have editorcam_from_game in user.cfg)
As for the keybind files themselves, I think this is how they work:
user.bnd is the 'active' set of keybinds, in other words, the game/dromed reads from that file.
However, if you go in to the game's Options menu, when you leave, it regenerates user.bnd by combining the current set of game controls (run, crouch, select sword etc) with the dromed controls which are read from default.bnd. If user.bnd does not exist, the controls are read from dark.bnd (t2 defaults) or the keys chosen if you change things from the Controls menu.
It's not absolute though. I think if you override any keybind (in user.bnd) with a dromed-only command, they remain in memory (unless you load a set of keybinds from the game menus).
Oh and I think dromed only reads user.bnd in game mode, and it edit mode still uses default.bnd :weird:
And (as if the above wasn't enough) I also think you can override the Dromed commands that go into user.bnd by editing the .bnd files in Saves (where gameplay keybinds are saved/loaded from the menus). For some reason my saves\cfg0004.bnd has one line for alt+g as "run .\cmds\gamemode.cmd", which is also in user.bnd, but that cmd file doesn't exist for me because it did things that aren't necessary under NewDark. Default.bnd has alt+g as game_mode