Unna Oertdottir on 6/5/2016 at 09:13
Nice find, Daraan :thumb:
Ricebug on 6/5/2016 at 11:44
You cycle through each object normally and add it to the queue (quick-link add)
Added (trolpts) to the queue. Now how do I CD link the complete patrol path?
Daraan on 6/5/2016 at 14:00
Quote Posted by Ricebug
Added (trolpts) to the queue. Now how do I CD link the complete patrol path?
So first to make sure it's working, are there arrows drawn between the objects?
If you finished your path: quick-link create and a popup menu should appear where you can select the flavour. If the last obj should be linked to the first to make a circle and if the queued objects shall not be removed for example adding a second link flavour. If ticked you still can add/remove/insert more objs into the queue.
manually command its quick-link create flavour + optional parameters 1,2,3
R Soul on 23/8/2019 at 19:27
This could do with some fixes. Startup.cmd has the commands light_bright and lit_obj_toggle, which are deprecated (see modders notes). I don't think any lighting commands should be in here. Even if most of us immediately turn on the lights in Dromed, I prefer the initial view to have shadows.
There's an old version of GoalMaster in there. I released a minor update so it's now version 1.01: (
https://www.ttlg.com/forums/showthread.php?t=145938)
DEOCI has been replaced with BinMaster: (
https://www.ttlg.com/forums/showthread.php?t=149975)
The Tools folder has something called 'OldDark Installs'. This must have been left in by mistake. ;)
Also in Tools is '3ds to bin'. The spaces must be removed from that folder name otherwise the program therein cannot create AI meshes (it calls a command line tool and the spaces in the file paths cause errors).
vfig on 29/5/2020 at 21:06
A very minor issue, but in beta 4 default.bnd has:
Code:
edit bind 9+ctrl "brush_color 3" ; terrain darkened when non-terrain brush selected
This description is incorrect. "brush_color 3" colors by how far away in time they are from the brush/obj that was selected when this mode was activated.
Daft Mugi on 16/7/2024 at 23:38
I discovered an issue with
EditModeAtPlr.cmd.
It is working by coincidence, because if the last line of a ".cmd" file does not end in a newline, it does not get executed.
Released version (1.14 Beta4) works:
Code:
set editorcam_from_game\r\nedit_mode\r\nunset editorcam_from_game
In the released version,
editorcam_from_game stays set because the
unset line is never called. This can be checked with
ifdef editorcam_from_game mprint is_set and
ifndef editorcam_from_game mprint not_set.
Edited version is broken because of the added
\r\n at end of file:
Code:
set editorcam_from_game\r\nedit_mode\r\nunset editorcam_from_game\r\n
When folks edit the file, its functionality will break if a newline is added at the end of file, acting just like
EditMode.cmd instead.
Therefore,
EditModeAtPlr.cmd should really just be:
Code:
set editorcam_from_game
edit_mode
mxleader on 9/9/2024 at 02:10
So what happens if I open an old mission in the latest tool kit version of DromEd? Does the mission blow up?
Also, I have the latest took kit installed but when I try to open Dromed a prompt appears and says AngelLoader is running, but it isn't. Then it says to change a line in the Cam_Mod file but I have no idea what to change. Any ideas?
FenPhoenix on 9/9/2024 at 10:18
In cam_mod.ini you find the line:
fm_selector C:\AngelLoader\AngelLoader_Stub.dll
(or similar)
and you change it to
fm_selector fmsel.dll
or most probably the line ";fm_selector fmsel.dll" already exists and you can just put a ; in front of the AngelLoader one and remove the ; from the fmsel one
Also you could find the line "fm" and change it to ";fm" (that will prevent fmsel from launching when you open DromEd)
Or, you could make a separate clean Thief install and put DromEd in there, to avoid this whole thing.
Long-winded explanation:
AngelLoader has to temporarily modify cam_mod.ini in order to run the game from in-app, and it will remove the modifications when it exits. The message you're seeing is a fallback in case somehow AngelLoader was shut down incorrectly or something and cam_mod.ini did not get changed back. If you copied your Thief folder to a new one while AngelLoader was running, it would cause cam_mod.ini to not be changed back in the new copy because AngelLoader doesn't know about it. Same thing if you made a clean Thief install but just copied cam_mod.ini from your old one while AngelLoader was running. Other than that I don't know any normal situation where this would happen, but I don't know your setup exactly.
mxleader on 9/9/2024 at 14:28
Thanks for the explanation. Does it make any difference if you open DromEd through AngelLoader or on it's own?
