Quote:
|
Originally Posted by panthercules
Thanks for your post - I'd seen some stray references to SH3 Gen but somehow had missed getting around to checking it out. It looks very cool, and I'm definitely going to play around with it some more.
Unfortunately, however, there is a truncation effect as you mention below:
"Another important thing is that no entry must be longer than 255 characters. Even though SHIII will load and display the text correctly the first time, it will not save it, and therefore the entry will be truncated at the next reload."
This truncation effect is definitely interfering with the "personal entries" portion of my modified log file approach. Basically, with this truncation effect the personal entries have to be so short that the process loses a lot of its fun/appeal.
This truncation appears to be a result of something SH3 Gen is doing, rather than SH3 itself - I have had no problem with personal diary log entries much longer than 255 characters both being displayed in game and being saved down into the next saved game's log file, but when I run SH3 Gen on the new saved game and then look at the log in game, the entries have indeed been truncated. Do you have any idea why this truncation occurs with SH3 Gen and do you think there is any way it can be fixed/tweaked so that it won't truncate the entries in this fashion? I'd love to play around with SH3 Gen now that I've discovered it, but I'd hate to have to give up my newly-personalized captain's log to do so.
[edit] - BTW - I D/L'ed and am using the .NET 2.0 version 0.7.1 of SH3 Gen, in case that matters.
|
That's something I cannot confirm right now. I think that this behaviour is not related to Sh3Gen in any way.
In fact, I would expect this kind of problem is caused by a too tiny array declaration in SHIII's .clg write routine. In other words, some programmer had a bad day and declared
string entry[256] somewhere - had he simply typed, for example,
string[2048] we would be so much better off!
Of course, it might be that I screw up something through the use of a redundant tag (header, entrytype etc) - but I need confirmation. Right now I am not convinced.
HINT:
If you want to make a check, it is pretty simple. Use notepad to add a very long entry of at least 300-500 characters to the log. Load the savegame. Save it again under another name and reload this re-saved data. You will see that the text is truncated. You will also see that this is because the re-saved .clg does already contain the truncated entries (the glitch is in the writing, not the reading part).
If not, and you can confirm this with entries of 300, 400, 600 characters, please post here and contact me because this would definitely prove me wrong, and mean I screw up something.
Quote:
|
Originally Posted by panthercules
This truncation effect is definitely interfering with the "personal entries" portion of my modified log file approach. Basically, with this truncation effect the personal entries have to be so short that the process loses a lot of its fun/appeal.
|
I split up the longer entries into 255 character blocks and don't find it a big problem anymore.