Editor Bug (Full Version)

All Forums >> [New Releases from Matrix Games] >> Gary Grigsby's War in the East Series >> Tech Support



Message

shane56 -> Editor Bug (10/1/2011 3:27:34 PM)

Evening,
updated my game to 105.28 and proceeded to edit my GC scenario..

loaded the scenario into the editor and checked it though it is missing the required data from my TOE files etc, as it is running off the generic files so I proceeded to the CSV tab and imported the CSV files relating to my GC scenario, and lo and behold all the exp, rdy & dam numbers for every unit, yep thats right for every single unit have disappeared and all are now zero.. What the naffing hell has happened here !!! [&:]

I cannot now work on my scenario as all the data is missing, and wont load in from the CSV's.. Has this happened to anyone else ?
To prove that it is not my csv file I loaded in another one from an earlier save and still the same result.
It looks as it if the editor now needs every unit to be rebuilt, after importing in the CSV, this obviously is definitely not going to happen.

It's a bug and needs fixing..
Only thing left to do is revert back to 105.23 and try it again [:(]

Shane



Helpless -> RE: Editor Bug (10/1/2011 9:00:18 PM)

It is not a bug. Unit CSV format was changed to reflect added data fields. It was stated in developement notes, but probably didn't go the release notes.

It means that you can't really use CSV files generated with previous versions. You need to import them back with old exe and export to CSV with newest version.




shane56 -> RE: Editor Bug (10/2/2011 5:54:07 AM)

quote:

It means that you can't really use CSV files generated with previous versions. You need to import them back with old exe and export to CSV with newest version


G'Day,
so going by what you said, I will have to set up a second earlier version of Wite, load in my senario then it's CSV file and then save out the scenario, then crank up the latest version of WitE load in the scenario and export the scenario out to CSV.
What about the generic files of the latest version interferring with all this ?
or do I also copy the generic files from the old version and over write the generic files of the new version ?

If this is not correct please give us a step by step process of how to effect this fix as you outlined above.
Thanks ..shane



Helpless -> RE: Editor Bug (10/2/2011 10:33:40 AM)

quote:

so going by what you said, I will have to set up a second earlier version of Wite, load in my senario then it's CSV file and then save out the scenario, then crank up the latest version of WitE load in the scenario and export the scenario out to CSV.


That's right.

quote:

What about the generic files of the latest version interferring with all this ?
or do I also copy the generic files from the old version and over write the generic files of the new version ?


Other then unit databases should import correctly with the latest exe.



shane56 -> RE: Editor Bug (10/2/2011 12:04:45 PM)


quote:

ORIGINAL: Helpless

quote:

so going by what you said, I will have to set up a second earlier version of Wite, load in my senario then it's CSV file and then save out the scenario, then crank up the latest version of WitE load in the scenario and export the scenario out to CSV.


That's right.

quote:

What about the generic files of the latest version interferring with all this ?
or do I also copy the generic files from the old version and over write the generic files of the new version ?


Other then unit databases should import correctly with the latest exe.



Evening,
sorry for laboring on this but I still cannot see how this will work loading it into the new version of wite as the new generic files will kill it every time, with the only way to over come this being to load in the CSV file, which is where it is failing now..
Will locking the files in the in the editor in the old version do the trick ? and prevent the new generic files from loading into the scenario ?

NOTE: this problem is a black hole that was not passed onto us the end user, and a work-around should have been clearly stated in detailed steps on how to over come this, rather than we just fall into this black hole and then have to drag our sorry carcasses out of it.. [:-]
Thanks ..shane



Helpless -> RE: Editor Bug (10/2/2011 1:06:14 PM)

i don't quite understand exact problem here, but locking generic data definitely would allow you to avoid the conflict with future updates.



shane56 -> RE: Editor Bug (10/2/2011 4:18:07 PM)


quote:

ORIGINAL: Helpless

i don't quite understand exact problem here, but locking generic data definitely would allow you to avoid the conflict with future updates.


Oh no.. this did not work !!!
I did everything as listed above and now I have some units with only partial data in them
It would appear that the additional TOE's and ground elements I setup at the bottom of these sections are not being loaded in even if I do a CSV import though when I check the actual CSV files they are still there.. AAArrrrgggg [:@]

I locked the files in the editor in the old version, saved the scenario, and copied it to the new version, loaded it, and exported it to the CSV in the new version, then shutdown the editor, and came back in and loaded the scenario up, imported the CSV and it did not work.

what with the amount of work I have put into my GC this is BS.. For pitty's sake, this editor is bugged and needs fixing..
Surely I cant be the only one suffering this ?
If you dont believe me then try this out yourself, using a previous scenario going through the steps as listed above.
Shane.. [&:]



Page: [1]

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
1.109375