bbb on 6/7/2015 at 17:10
Have a strange persistent player position issue that I probably caused.
I updated my laptop and had a T2 mission probably half done. I was building it with NewDark on the old laptop and installed T2/NewDark on the new laptop (a newer version of NewDark) and simply copied the mission file to the new laptop. It created a number of issues but one that I can't figure out is persistent player position does not work properly. Here is the situation. In Dromed I move the camera around to that I am in a different part of the mission and go into game mode and I am in the location I see on the Dromed screen which is fine. I then move around in game mode and when I Alt E out and go back into game mode, I am back where I was before I moved around in game mode. I don't think I am explaining this well. Let me describe and example. I am at the starting point and move to point A in Dromed. I go into game mode and I am at point A. I then move to point B (in game mode) and when I Alt E out of game mode, I am back at point A in Dromed.
The weird thing is persistent player position works fine with other files. I tried it with an old mission file of mine (Lord Matt) and it worked exactly as expected. Not sure if something got screwed up because I built the mission in one version of NewDark and am using a newer version of NewDark now.
in any case, if anyone has any ideas as to what would cause this issue and how to fix it I would greatly appreciate the help. If not, I will probably finish the mission on the older laptop (much slower and clunky).
Thanks for your help.
BBB
gamophyte on 6/7/2015 at 18:55
Persistent player position does just as you are describing. It will go into game mode where ever you are in the editor. What you want is "synch_to_playcam" which is new to 1.23. This will make editor view the same as where you were in-game.
Yandros on 6/7/2015 at 19:01
Exactly, what you describe is what has always been the behavior with persistent player position. I didn't know about the new flavor, so thanks for that gamophyte.
Renault on 6/7/2015 at 20:05
I think using the command "editorcam_from_game" fixes this as well, right?
LarryG on 6/7/2015 at 20:16
Wait a minute. With persistent_player_pos=1 you return to the starting point every time you enter game mode. With persistent_player_pos=0 you stay the location that you were at in editor mode when you enter game mode from editor mode. Is it doing anything different than that? The command persistent_player_pos is a toggle. Each time you use it, it will switch from 0 to 1 or from 1 to 0. Check monolog to see what it is currently set to.
ZylonBane on 6/7/2015 at 21:07
Ppp has no effect on where you end up when leaving game mode. What it affects is where you appear when ENTERING game mode.
LarryG on 6/7/2015 at 21:23
I stand corrected.
ffox on 12/7/2015 at 08:22
I've been playing with synch_to_playcam; it doesn't work for me when entered into any .cfg or .ini file, or when typed in as a command.
It works fine if you type it into the game mode console just before you exit DromEd game mode. It's a one-off; you will need to type it into the console again when you move to another position in game.
Ricebug on 12/7/2015 at 09:55
Let me throw in here. It doesn't seem to matter WHAT I have set in my USER.CFG. The player position ALWAYS starts at the start point, the light toggle is off, and the AI are alert. I have to manually toggle each one via the menus before going into the game via the editor.
From my cam.cfg, in case yer wonderin':
[INDENT]; general configs
include_user_cfg user.cfg
editor_include_dromed_cfg dromed.cfg[/INDENT]
In past installs, this stuff appeared in the monolog as a mission loaded. Now it doesn't.
nightshifter on 12/7/2015 at 15:18
@Ricebug... have a look in startup.cmd. a lot is set there. ( I presume you use the dromed toolkit)
about player position... try alt+R when going back to editor... did read about that new command somewhere. does the trick for me.
