Gray_Lensman wrote:From what I can tell by loading up the (beta 7) 56 to 63 scenario, the artillery in forts is still field artillery NOT heavy artillery.
22:02:28 [Error ] FullDebug: Script Engine Error(s), while parsing line 13468 MinDate = 16/09/56
22:02:28 [Error ] FullDebug: Script Engine Error(s), while parsing line 13469 MaxDate = 01/12/62
22:02:28 [Error ] FullDebug: Script Engine Error(s), while parsing line 13532 MinDate = 16/09/56
22:02:28 [Error ] FullDebug: Script Engine Error(s), while parsing line 13533 MaxDate = 01/12/62
22:02:28 [Error ] FullDebug: Script Engine Error(s), while parsing line 13548 MinDate = 16/09/56
22:02:28 [Error ] FullDebug: Script Engine Error(s), while parsing line 13549 MaxDate = 01/12/62
22:02:28 [Error ] FullDebug: Script Engine Error(s), while parsing line 13660 MinDate = 16/09/56
22:02:28 [Error ] FullDebug: Script Engine Error(s), while parsing line 13661 MaxDate = 01/12/62
22:02:28 [Error ] FullDebug: Script Engine Error(s), while parsing line 13900 MinDate = 16/09/56
22:02:28 [Error ] FullDebug: Script Engine Error(s), while parsing line 13901 MaxDate = 01/12/62
22:02:28 [Error ] FullDebug: Script Engine Error(s), while parsing line 14156 MinDate = 16/09/56
22:02:28 [Error ] FullDebug: Script Engine Error(s), while parsing line 14157 MaxDate = 01/12/62
22:02:28 [Error ] FullDebug: Script Engine Error(s), while parsing line 14204 MinDate = 16/09/56
22:02:28 [Error ] FullDebug: Script Engine Error(s), while parsing line 14205 MaxDate = 01/12/62
22:02:28 (Reporting) FullDebug: Script Engine, while parsing line 28516 Unknown Keyword: --------------
22:02:28 [Error ] Errors found in script: 14 Check C:\Program Files\Rise of Prussia\ROP\Scripts\ScriptReport.txt
[The extension txt has been deactivated and can no longer be displayed.]
Gray_Lensman wrote:Ebbingford (and others who might be interested in some debugging info:
Using the first line of your error messages:
We can look into your posted (linked) ScriptReport.txt to find the following:
Now, we search for the particular event (.sct) file that would contain the specific event referenced above... i.e. evt_nam_PRU_aggro1Bohemia2
Most if not all .sct files reside in the .../Events/... folder in the AGE game system.
So... searching results find that particular event does in fact reside in the PrussianAI.sct event file and has the following syntax:
Not only does the MinDate and MaxDate NOT use the proper format in this particular event (for ROP). It turns out this particular event file is totally screwed up in that most if not all of the other events' MinDate/MaxDate syntax in that same file are also screwed up...
Interesting though... The same types of commands in the AACW event files use the format yyyy/mm/dd. This could be where the mistake was made, presuming that whoever put together these events was used to the previous syntax format. Seems that this was an unnecessary/irrational syntax switch and makes me wonder why, since we are continuously working on what I presumed to be similar event syntax statements for all game designs using the AGE game engine. Going from one AGE game database file to another is going to naturally result in these types of errors when making these types of unnecessary/irrational syntax changes in an event command that is used in all of the AGE games.
Good find...
Incidentally, had you not posted the ScriptReport.txt file, I would have had to ask for the saved game files in order to rerun the turn to generate that same file for the above debugging work. You did very good in posting the ScriptReport.txt along with your bug report here. Thanks Again.
I'm not sure WHO is the end point of contact for ROP database corrections... Not me at this time... BUT whoever is, will obviously need to correct the source database file(s) and regenerate the .sct file(s) for the necessary followup patch. The CSVSplitter.exe file that I have would not output this new syntax correctly anyhow since it does not have a distinction for ROP output files.
To wit:
[ATTACH]12623[/ATTACH]
Notice there is NO distinction for ROP output file extractions in the CSVSplitter that I'm using which is the latest one that modders can download from the Official Files for Modding thread located in the Modding AGE Engine Games SubForum updated June 3rd 2010 per that same thread.
No wonder Modders give up and MOD the text based output files directly when even the volunteer coordinators can't get the latest version of the proper CSVSplitter program.
Gray_Lensman wrote:Interesting... I was assuming that with the implied incorrect format error message, that the problem was caused by having an out of date CSVSplitter, especially since 0.71 has designated buttons for the different AGE engine games but not for ROP where this problem showed up. It just seemed logical that this issue would have been the type of issue to be sorted out/compensated for in the splitter program (by using the game specific buttons) if ROP was expecting a different output syntax format than the other games. Who would expect the .xls (Excel) date format to have to be different for different games in the AGE game system anyway?
Also I could not find the source .xls file for the PrussianAI.sct file in the current ROP_DB.zip file collection to double check the .xls format. Is it included there and I overlooked it, or is it a new file not posted in that grouping?
So the mystery deepens... Why does the ROP engine output error messages that state a different format needed than the other AACW/AGE games?
Gray_Lensman wrote:Exactly, the dates look identical to all the other games' output files that I've looked thru, Yet there is an error AND the error message states the cause of the error to be a different syntax is required. One can quite easily assume that this was an issue that was supposed to be compensated for in an updated/newer CSVSplitter program.
It'll be interesting to find out the correct source of this error.
Line 12310: SelectFaction, selected: Prussia
Line 12311: Started processing event: evt_nam_PRU_Leader_AIActivate
Line 12311: This event is not yet referenced, base number of allowed occurences 999
Line 12314: Min date evaluated: 1756/01/01 converted to turn 3745 current turn 3762 True
Line 12316: CheckAILevel: Checking AI Level of faction Prussia at least equal to 1 True
Line 12317: ActorEnabled : False
Line 12325: Finished processing event: evt_nam_PRU_Leader_AIActivate
Line 12973: SelectFaction, selected: Austria
Line 12974: Started processing event: evt_nam_AUS_Leader_AIActivate
Line 12974: This event is not yet referenced, base number of allowed occurences 999
Line 12977: Min date evaluated: 1756/01/01 converted to turn 3745 current turn 3762 True
Line 12979: CheckAILevel: Checking AI Level of faction Austria at least equal to 1 False
Line 12988: Finished processing event: evt_nam_AUS_Leader_AIActivate
Line 13460: SelectFaction, selected: Prussia
Line 13461: Started processing event: evt_nam_PRU_aggro1Bohemia2
Line 13461: This event is not yet referenced, base number of allowed occurences 999
Line 13464: TurnIndex: Testing 17 vs current turn index: 17 True
Line 13465: Probability evaluated: Probability 10 rolled 10 True
Line 13467: CheckAILevel: Checking AI Level of faction Prussia at least equal to 1 True
Line 13468: => CheckMinDate command, Erroneous format for date, need yyyy.mm.dd or dd/mm/yyyy
Line 13469: => CheckMaxDate command, Erroneous format for date, need yyyy.mm.dd or dd/mm/yyyy
Line 13471: Entering triggered actions for event evt_nam_PRU_aggro1Bohemia2
Line 13472: AI.ChgAggro Prussia Aggressivity coeff in Theater 73 is now at 90
Line 13474: Finished processing event: evt_nam_PRU_aggro1Bohemia2
Ebbingford wrote:Playing as Austria, long campaign.
Still getting the following error messages at end of turn processing, game carries on OK though.
Script report attached if needed.
23:44:45 [Error ] FullDebug: Script Engine Error(s), while parsing line 13484 MinDate = 16/09/56
23:44:45 [Error ] FullDebug: Script Engine Error(s), while parsing line 13485 MaxDate = 01/12/62
23:44:45 [Error ] FullDebug: Script Engine Error(s), while parsing line 13500 MinDate = 16/09/56
23:44:45 [Error ] FullDebug: Script Engine Error(s), while parsing line 13501 MaxDate = 01/12/62
23:44:45 [Error ] FullDebug: Script Engine Error(s), while parsing line 13724 MinDate = 16/09/56
23:44:45 [Error ] FullDebug: Script Engine Error(s), while parsing line 13725 MaxDate = 01/12/62
23:44:45 [Error ] FullDebug: Script Engine Error(s), while parsing line 13788 MinDate = 16/09/56
23:44:45 [Error ] FullDebug: Script Engine Error(s), while parsing line 13789 MaxDate = 01/12/62
23:44:45 [Error ] FullDebug: Script Engine Error(s), while parsing line 13868 MinDate = 16/09/56
23:44:45 [Error ] FullDebug: Script Engine Error(s), while parsing line 13869 MaxDate = 01/12/62
23:44:45 (Reporting) FullDebug: Script Engine, while parsing line 28516 Unknown Keyword: --------------
23:44:45 [Error ] Errors found in script: 10 Check C:\Program Files\Rise of Prussia\ROP\Scripts\ScriptReport.txt
Gray_Lensman wrote:Here's another idea that has worked in the past
Has anyone thought to go into the PrussianAI.sct file or source DB file and switch the conditions orders to have the CheckAILevel condition follow the MaxDate and MinDate conditions?
_______________________________________
Sent from my Droid X using Swype.
Return to “Help to improve RoP”
Users browsing this forum: No registered users and 5 guests