Daraan on 5/8/2013 at 18:27
ah DJ that update came a bit to late for me. Installed yesterday with 2.10 on my new comp.
Well I will manually update the Fix pack and compare the dromed_basic with my own setup don't want the TP to mess arround again:joke:
There's a point I have criticize it's the mods folder. I installed with TP and then copied my custom stuff into the folder for example I replaced for standard sword model with another one but the problem is that NewDark loads the mods folder before anything else and so my custom stuff (with same names) is ignored.
So I would prefer a install method which is based on darkinst entry only like you did it for patchedres.
Anyway thanks a lot for making new version.
DJ Riff on 6/8/2013 at 07:16
The mods folders are listed in cam_mod.ini in strings named mod_path and uber_mod_path. The structure is the same as in darkinst.cfg. So if you want to use the folder with your modded content, you can add it to the mod_path in front of all other folders listed - this will make your folder higher priority. You can also add the .\mods folder itself and dump your stuff right there.
The folder priorities are like this:
uber_mod_path > FM folder > mod_path > root > darkinst folders
Folders listed in mod_path may contain any content like *.gam, *.mis, *.osm files in addition to resource files. When using darkinst, you have to specify folders with such files in load_path and script_module_path AND have original files removed from the root folder as the root has higher priority than darkinst folders.
Infinitron on 6/8/2013 at 13:31
I think this new version does something weird to the "SlowFrameUI" setting in cam_ext.cfg (replaces it with SlowFrame)
DJ Riff on 6/8/2013 at 15:49
Quote Posted by Infinitron
I think this new version does something weird to the "SlowFrameUI" setting in cam_ext.cfg (replaces it with SlowFrame)
They are two different settings.
Code:
; framerate cap for menu system (specified as minimum frame time in ms), reduces GPU and CPU load in menus
SlowFrameUI 10
; set minimum frame time value to 1ms to avoid speedups at high framerates, this does NOT cap the framerate
; it only sets the lower frame time limit so that if a frame is shorter than this, the engine will pretend
; that it was this long
min_frame_time 1
; cap engine update frequency to 250 Hz (specified as min updated time in ms), for a software framerate cap when
; using "single_display_mode" it's probably better to use "framerate_cap", this is just a last resort cap
SlowFrame 4
Infinitron on 6/8/2013 at 17:58
Yes, there are. I'm saying your installer replaced the first one with the second one, so the latter was duplicated.
DJ Riff on 7/8/2013 at 05:21
Well, the config handling code haven't changed from 2.0.10, so if there's a bug, it's present in 2.0.10 too. I'll do some testing, thanks for the info.
Infinitron on 9/8/2013 at 00:16
I noticed that the installer also adds redundant lines to cam_ext.cfg. For instance, if the original file has:
Code:
d3d_disp_scaled_2d_overlay 64
then the modified one gets:
Code:
d3d_disp_scaled_2d_overlay 64
;d3d_disp_scaled_2d_overlay 64
DJ Riff on 9/8/2013 at 16:05
It's intentional. Actually, when TP updates NewDark, it places the new cam_ext.cfg from the new NewDark package to ensure all options are compatible. Then it reads the old one and modifies variables in new one accordingly. If the variable is commented out by default, but the old one is uncommented, it will add it somewhere near the commented one. It's done this way so that if the line contains some useful commentaries in addition or an example of the string syntax it won't be erased. The only exception are binary variables which contains no parameter — commented ones will be uncommented but only if they don't contain any additional symbols. If TP doesn't find the appropriate place for a variable (no commented one exists in the default file), it will add it to the bottom of the file, that's a normal behavior too.
