Sensut on 14/3/2013 at 17:33
Whoever you are, thanks so much! :thumb: Especially for these:
- fixed sky (non-)rendering bug when texture palette contained more than 246 textures
- fixed crash bug when selecting sky surface if texture palette contains more than 246 textures and editor is using software rendering
LarryG on 14/3/2013 at 17:36
:wot: There are more things fixed than I knew were wrong!
And I thought Xmas this year was over. What a nice present. Thank you. :thumb:
ZylonBane on 14/3/2013 at 17:47
Quote Posted by LarryG
And I thought Xmas this year was over.
Uhm... you might want to demand a refund from whoever sold you your calendar.
kdau on 14/3/2013 at 18:46
Although the 1.20 documentation does say that it can still open 1.18/1.19 missions/saves, I didn't see anything about 1.19 being able to play 1.20 missions. (Though none of the changes suggested any problem.) To be sure, I opened a small 1.19 mission with the 1.20 dromed.exe, did complete processing, saved, and then played it in the 1.19 thief2.exe, with no problems. So it seems we won't have to force players to re-upgrade, although I suppose we should at least cajole them to do so. :cool:
ZylonBane on 14/3/2013 at 18:52
Quote Posted by kdau
So it seems we won't have to force players to re-upgrade
This is a terrible, terrible, terrible, terrible, terrible line of thought.
sNeaksieGarrett on 14/3/2013 at 19:00
Wow awesome! Thanks for the news Squadarofl!
Particularly happy about the windows icon bug being fixed, I had that one personally.
kdau on 14/3/2013 at 20:13
Quote Posted by ZylonBane
This is a terrible, terrible, terrible, terrible, terrible line of thought.
Well I'm certainly not encouraging anyone to keep using 1.19, but as a developer (in this community or otherwise) I don't feel it's my place to add system requirements to my work that aren't strictly necessary. We can't be sure exactly how any given player has come to install NewDark, or if some technical, language, or other barrier might have stopped them from knowing about later patch versions or being able to install them. A warning about being out of date is one thing, but personally I don't like having my options arbitrarily limited by someone who doesn't know my situation.
Now, it is of course up to every author how to handle it. And if an author were using some 1.20-specific feature or doing something they knew would be broken by an unfixed bug in 1.19, that would be entirely different. (In fact, since there
isn't any automatic warning or error, I guess we're back to the old days of big red notices in readme files.) But for me personally, without one of those situations, the most I'm willing to do is inform the player and hope for the best.
That said, would anyone be interested in a script like VersionCheck (from version.osm) that checked for a minimum version of the engine and sent TurnOn/TurnOff as appropriate?
kdau on 14/3/2013 at 21:09
Thanks, good to know that's available---it should probably be listed in one of the stickies. But I actually mean one that checks the version of thief2.exe, not just one that checks versions of OSMs but is compatible with NewDark. Now that there is more than one NewDark version out there, we could potentially need to worry about both engine and OSM versions. I suppose it would make sense to just extend VersionCheck to accept a parameter such as GameVersion=1.20 in addition to script module names.
LarryG on 14/3/2013 at 21:16
Well, the source is there in the zip, so go for it.
