howdy Quintillus,
found an apparent error running 032.
when i ...
- load an uncompressed version of the standard c3c BIQ file
- enter "test" in the output file name
- leave everything else at the default
- hit the export button
.. i get an empty file. yes, i KNOW that's _technically_ what i asked for! [*grin*] however, it aint what i was expecting. i was expecting an error msg saying that i had to choose SOMETHING to export.
could you / would you either add such an "error" response or perhaps simply gray out that section of the ui until one selects _something_ to export?
again, thanks for the nifty util! [*grin*]
take care,
lee
That's called the computer doing what you told it to do.
And indeed it's what I would expect it to do. But you've certainly got a point that it doesn't make much sense to be able to export a blank file. I'll probably disable the Export button until
something is selected in a future version.
howdy Quintillus,
another possible error with 032.
loaded the same uncompressed version of the standard c3c BIQ file, selected ONLY "additional scenario properties" and exported that.
lookee ...
"
victoryConditionsAndRules: 262144
dominationEnabled: false
spaceRaceEnabled: false
diplomacticEnabled: false
conquestEnabled: false
culturalEnabled: false
civSpecificAbilitiesEnabled: false
culturallyLinkedStart: false
restartPlayersEnabled: false
preserveRandomSeed: false
acceleratedProduction: false
eliminationEnabled: false
regicideEnabled: false
massRegicideEnabled: false
victoryLocationsEnabled: false
captureTheFlag: false
allowCulturalConversions: false
wonderVictoryEnabled: false
reverseCaptureTheFlag: false
"
shouldn't SOME of those be TRUE? [*grin*] from my eyeballing of the standard BIQ file, it seems at least the 1st five of those should be TRUE.
take care,
lee
Hmm, now that does
look like a bug. And there actually is a bug in that part - I forgot a line of code. Hence an update is coming. However, given the value of 262144 for victoryConditionsAndRules, I think you would have received those results anyways. The reason is that 262144 = 2
18. And there are 18 traits - each one corresponds up to a power of two, up through 2
17. So if you have all of them true, you only get 262143. For a value of 262144, you'd have to have only the bit
after the ones Civ3 uses be enabled. And if 262144 were the value the file used, Civ3 Conquests Edit would see all the properties as being disabled - false. If you had 262144+262143 (or 262143) as the value of that integer, Civ3ConquestsEdit would see all the values as being true.
Hex editing of one of my scenario files confirms that 262144 leads to all false, and 262143 to all true. My prediction is that if you load up the file you tested in Civ3 Conquests Edit, you'll see all those as being false. If you had had any value between 1 and 262143, you would indeed have stumbled upon the bug of it returning all false when it isn't supposed to.
I'm curious how you got a 262144 BIQ though. The bit that leads to 262144 shouldn't be being used, and Civ3ConquestsEdit keeps chalking up 0's when I create a new scenario for me, or 33247 if I enable custom victory conditions/scenario property rules but don't change anything. If these 262144's are in widespread circulation I may have to modify a bit of code. I can't tell any difference between a 262144 and a 0 in the official editor, though.
edit: New version with that bug squashed is up. It's 18 KB larger, but that's not because of that one line of code - that's work on the Compare Mode that's not enabled yet. Right now Compare Mode is doing something in the very limited subset I've coded - not quite what it's supposed to, but it's definitely going to be coming fairly soon.