R Soul on 25/2/2023 at 17:19
I've recently gotten into the habit of moving the starting point so that when the mission is loaded, the camera is already at the place I've been working on.
Turning off persistent_player_pos and using the editorcam_from_game config var are fine
during an editing session, but not with mission loading.
I made a .cmd file which runs these commands:
Code:
cam_marker
copy_props_to start
delete_brush
Things to note:
Blank line at the end, required for all DromEd .cmd files
"start" is object name I use for the starting point. I'm not sure if the command would work for something with a space in its name.
The first command creates a marker where the camera is, and at the same angle.
Since the only property on the marker is Position, that's the only thing that will change with the starting point.
The marker will remain selected, so the third command will go for the correct object.
Most dromed toolkit packages put .cmd files in a Cmds folder, so I've stuck with that convension.
In Menus.cfg I've put it on its own, but it's enturely down to user preference:
In the ;Menu descriptors section, I added this after the EAX menu name:
Code:
| Starting Point:
menu_startAt the end of the file (can probably be in any location)
Code:
menu_start Start to Camera:run .\cmds\StartToCam.cmd
Hit Deity on 26/2/2023 at 02:33
Gonna have to try it out
Hit Deity on 26/2/2023 at 17:32
Yup, seems to work no matter what I named it, although I did not try any crazy combos, no special characters, nothing like that..
But what does in fact work is
spoint
StartingPoint
S Point
s_Point
Capitalization didn't seem to matter at all, but spacing and placement of the underscore did, as expected.
