Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.
Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).
I'm working on updating ShipWrite, Mission Control and WeaponSmith for EVO 1.0.2. The updated bible describes some new fields and flags which is good, but the TMPLs in the resEdit file show templates that are much larger that the description in the Bible, including many 'unused' fields. If I am making new resources do I have to match the size and structures implied by the TMPLs or just the fields in the Bible? I am guessing the additional undocumented fields will be used in EV3. Do I fill them with zeros?
How does EVO 1.0.2 cope with old EVO 1.0.1 plugins, does it identify resource versions by size? Any information about these issues will be gratefully recieved. The sooner it is sorted out the sooner the updates will be available.
cheers Ralph
------------------ R & R Software
Quote
Originally posted by Ralph: **I'm working on updating ShipWrite, Mission Control and WeaponSmith for EVO 1.0.2. The updated bible describes some new fields and flags which is good, but the TMPLs in the resEdit file show templates that are much larger that the description in the Bible, including many 'unused' fields. If I am making new resources do I have to match the size and structures implied by the TMPLs or just the fields in the Bible? I am guessing the additional undocumented fields will be used in EV3. Do I fill them with zeros?
i don't think it matters, since they're UNUSED
How does EVO 1.0.2 cope with old EVO 1.0.1 plugins**
Any plugins made for 1.0.1 (and probably 1.0.0 aswell) should work with 1.0.2
------------------
If I were you, I'd fill them with -1 as that's what I do and they don't seem to have any effect. I think they're just spare fields that were going to be used for something but then got dropped. I thought I heard Andrew (welch) saying that the templates for EV3 were going to be drasticly different.
------------------ Marge: Pointing to Circuit board in Robots opened head See Homer, that's why your robot didn't work!
(url="http://"http://www.AmbrosiaSW.com/cgi-bin/ubb/newsdisplay.cgi?action=topics&number;=20&forum;=*EV/EVO+chronicles&DaysPrune;=25&article;=000024&startpoint;=")The Tides of War(/url)
AIM: HipHopJack
Right, I've discovered a range of EVO ship resource sizes can be found in EVO itself, let alone when you check out other plugins. The EVO 1.0.2 Resedit TMPLs describe a 114 byte stucture, including 8 Unused DWRDs at the end. Some EVO ships appear to have 112 byte ships! Anyway I am reading in ship resources, and expanding whatever I find up to 114 bytes, padding with -1s, and setting Fuelregen, ShotXOffset and SkillVar to 0 is they are not already set. Once saved, ShipWrite will leave ships in the 114 byte format. Anyone see anything wrong with this?
Ralph
Originally posted by Ralph: **Right, I've discovered a range of EVO ship resource sizes can be found in EVO itself, let alone when you check out other plugins. The EVO 1.0.2 Resedit TMPLs describe a 114 byte stucture, including 8 Unused DWRDs at the end. Some EVO ships appear to have 112 byte ships! Anyway I am reading in ship resources, and expanding whatever I find up to 114 bytes, padding with -1s, and setting Fuelregen, ShotXOffset and SkillVar to 0 is they are not already set. Once saved, ShipWrite will leave ships in the 114 byte format. Anyone see anything wrong with this?
**
Not at all. You guys are making great stuff, but I do have one question. Do you ever sleep?
------------------ "Holy F***! HeΒs got my ass!!Β - A friend of mine right after the roller coaster we were on started to work again.
(url="http://"http://www.joljvik.com")The New Website!(/url)