(not a bug) Is the compile flag in dsb.ini active?
Moderator: Sophia
Forum rules
Please read the Forum rules and policies before posting.
Please read the Forum rules and policies before posting.
(not a bug) Is the compile flag in dsb.ini active?
I have been experimenting with dungeon design for DSB and it seems that I have to delete dungeon.dsb in order to get the system to regenerate and take account of changes regardless of the setting of the Compile flag in dsb.ini. Likewise, I have to delete dungeon.dsb in all of the dungeons regardless of the Compile flag when a new beta of DSB comes out. Bug, not implemented yet, or am I missing something?
- Sophia
- Concise and Honest
- Posts: 4240
- Joined: Thu Sep 12, 2002 9:50 pm
- Location: Nowhere in particular
- Contact:
Odd.
Ok, a few more tests.
First, let's determine if dsb.ini is even being read properly. Right now, all of the values in there are default (that is, the program would work the same even if the file didn't exist at all)-- try changing Windowed=0 to Windowed=1, and see if the program comes up windowed.
If it doesn't, that means dsb.ini isn't even being read. If it's not able to even read dsb.ini make sure that your shortcut to DSB.exe has "Start in" set to wherever DSB actually is installed. If that is correct and it still can't find dsb.ini then this is probably a bug I'll have to fix.
If it does come up windowed, then could you paste the last few lines of log.txt during a time when Compile=1 is set and it should be overwriting a dungeon.dsb but isn't? The main line I'm looking for is "Parsing some/path/here/dungeon.lua" which confirms the file is being loaded from a Lua script.
Ok, a few more tests.
First, let's determine if dsb.ini is even being read properly. Right now, all of the values in there are default (that is, the program would work the same even if the file didn't exist at all)-- try changing Windowed=0 to Windowed=1, and see if the program comes up windowed.
If it doesn't, that means dsb.ini isn't even being read. If it's not able to even read dsb.ini make sure that your shortcut to DSB.exe has "Start in" set to wherever DSB actually is installed. If that is correct and it still can't find dsb.ini then this is probably a bug I'll have to fix.
If it does come up windowed, then could you paste the last few lines of log.txt during a time when Compile=1 is set and it should be overwriting a dungeon.dsb but isn't? The main line I'm looking for is "Parsing some/path/here/dungeon.lua" which confirms the file is being loaded from a Lua script.
Well, it claims to parse the configuration file even if it isn't there.
Just a question:
Just a question:
You said "in my dungeons" -- does that mean you have .ini files in the same folders as your dungeons? Because the only 'dsb.ini' file that matters is the one that's in the same directory as 'DSB.exe'. If that's not the one you're modifying, none of your changes will apply.here is the dsb.ini I use in my dungeons