Unna Oertdottir on 5/4/2018 at 11:14
Indeed. That's where I found it years ago :)
Tannar on 10/11/2018 at 01:08
Pukey Brunster and I had the same error that Vfig had in the first post. We thought our experience might help others.
We're using ND 1.26, and we'd changed the max_obj number to 8192 per the new limits listed in the ND modder's notes. That resulted in the Assertion error. After finding this thread, Pukey used Una's suggested numbers for Obj_min (-18192), Obj_max (8184) and Max refs (47740) in Dark.cfg, but running pathfinding resulted in the original warning being generated in monolog non-stop during the process, and after almost an hour the process was still running with no end in sight.
Thinking her gamesys was borked at this point, Pukey sent me a copy of her .cow file (along with her texture folders because we both have some recolored textures, etc.) I changed my numbers in Dark.cfg to match Una's also, and then loaded the .cow. I ran pathfinding but still got the error. I then ran the resize_obj_id_space command in the command window, and in the pop up box entered Una's suggested values for Obj_min and Obj_max. I then ran pathfinding again and this time it completed with no errors. I saved the .cow, closed and restarted dromed and loaded the new .cow. It loaded with no errors or warnings and all is back to normal.
So for those encountering this error for the same reason, it might be worth sending the .cow to someone else to resize the object ID space and run pathfinding. Also, it seems that, for us at least, just changing the values in Dark.cfg wasn't enough, we also had to run the resize_obj_id_space command with those same values.
vfig on 10/11/2018 at 11:22
Quote Posted by Tannar
we also had to run the resize_obj_id_space command with those same values.
Ah, so that's why I kept running into the problem even after editing dark.cfg: I was reopening the same .mis with the old limits baked into it! (It seemed to fix itself when I used a different Dromed installation simply because I then created a new file, unwittingly! Lots of facepalm for me)
Unna Oertdottir on 10/11/2018 at 11:41
Maybe this is the case if the obj ID space is completetly 'full'. How many objects did you have? Deleting some of them before editing dark.cfg might help.
john9818a on 11/11/2018 at 05:47
Is the resize_obj_id_space a ND command? I vaguely remember whenever the obj_max value was increased in old dromed, changing it back to a lower value had no effect.
SneakyGuy101 on 18/1/2020 at 08:49
Was having some issues with obj_min but this thread helped greatly and I figured my problem out :thumb:
