jdog5000
Revolutionary
Hmmm ... okay. I thought the issue with your save was the same as with JimMac's, will check again.
@dexy Are you using Afforess' modmod? If you are not, Rom does not change the Dll from Revdcm. I do not know if that means anything though.
What happens if you play on a really small map? Like Duel size?
Also, what version of BBAI are you using? (shown by mousing over the big flag next to the minimap)
Hi,
I play RoM 2.71 which includes RevDCM 2.5 and I get a CTD every 3-5 turns, but it can't be reproduced for sure at the end of some turn (I guess there's some randomness there).
What I see when I use JIT debug is that the problem always arises from the method CvPlot::isHasPathToEnemyCity(), when you do gDLL->getFAStarIFace()->Initialize(...).
Hope this helps. I can post a save, but you won't get a certain CTD for a couple of turns.
Dexy
RoM is so big, it doesn't demonstrate anything using it as an example.
I try so hard with my mod not to deviate from RevDCM, but I still need to triple check things. Also I've been right every time so far when people playing RoM blame RevDCM for hangs and crashes; RoM has been the cause of the crashes, not RevDCM.
Pure RevDCM has several asserts on loadup, at least for me on a debug build. So there are bugs there. Not major, but they exist. Since RoM has unaltered RevDCM SDK, I seriously doubt it is the cause of any crashes. You have to try pretty hard to make python or XML crash a game, and then, it's pretty obvious why it crashed.Like I said before, if you can actually demonstrate a flaw in the RevDCM code, or get an assert showing the issue is one of AI logic, show it, but I'd wager a donut, actually I'd wager a dozen donuts, it's RoM code that's the problem.
I'm not sure if this is meant in jest or not, but I'll assume so. I care about all complaints.Afforess will probably fix it though. He's getting close to a stage where complaints such as yours will mean something.
Okay, the multi-player crash on colony creation has been fixed! Many thanks to TheOnlyDJCat for playing a few very short MP games with me to sort out the issues.
Actually it has been. The infinite loop bug which seems to get alot of complaints in the RoM forum was caused by some RoM code allowing for cargo promotions. Sure the fix needed to be made in the SDK, but it's not fair to expect RevDCM to locate bugs like these. They need to be found on RoM's end if it's RoM's code causing the issue. Whenever a bug occurs in a RevDCM merge it's a good idea to assume it's caused by the merger, not the RevDCM core, unless the merger can track the cause back to RevDCM code.RoM has not be the cause of the crashes. If you will wander over to the UP bug page, and see my report and fix, you'll see that one such bug was a problem in vanilla BTS that was never used before.
With 2.5 I can't replicate this. I only get 2 consistent asserts, that one that says "ignore this" and points to some bizzare file path, and seems to mean nothing, and the other one that checks for the pressence of NO_STATE religion, which makes no sense, and is obviously an issue, but doesn't seem to cause any problems.Pure RevDCM has several asserts on loadup, at least for me on a debug build. So there are bugs there. Not major, but they exist. Since RoM has unaltered RevDCM SDK, I seriously doubt it is the cause of any crashes. You have to try pretty hard to make python or XML crash a game, and then, it's pretty obvious why it crashed.
Actually I was being serious. Though I was smashed at the time, so my wording probably wasn't the most clear. Basically what I'm saying is that bugs experienced from large mergers should be handled in house first, and only reported here after someone with some knowlegde has checked the crash with a debug dll, and concluded it's something in the RevDCM core, and not a problem with the mod itself. With RoM, you're the person who will be the most responsive to check up on crash reports, so really the report should be handled and by yourself. Personally I don't want LoR users coming in to the RevDCM forums and reporting bugs they encounter with LoR here, I'd rather check it first, and be sure it's not a problem with my changes first. Same goes for RoM.I'm not sure if this is meant in jest or not, but I'll assume so. I care about all complaints.
Okay, the multi-player crash on colony creation has been fixed! Many thanks to TheOnlyDJCat for playing a few very short MP games with me to sort out the issues.
For those of you keeping score at home, the root of the problem was a fix for another bug ... .
For those of you with multiplayer games in progress or who want to play multiplayer, I've uploaded a new version to the development version download. It's labeled a pre-release version of 0.82, but should be stable. . .
Actually it has been. The infinite loop bug which seems to get alot of complaints in the RoM forum was caused by some RoM code allowing for cargo promotions. Sure the fix needed to be made in the SDK, but it's not fair to expect RevDCM to locate bugs like these. They need to be found on RoM's end if it's RoM's code causing the issue. Whenever a bug occurs in a RevDCM merge it's a good idea to assume it's caused by the merger, not the RevDCM core, unless the merger can track the cause back to RevDCM code.
With 2.5 I can't replicate this. I only get 2 consistent asserts, that one that says "ignore this" and points to some bizzare file path, and seems to mean nothing, and the other one that checks for the pressence of NO_STATE religion, which makes no sense, and is obviously an issue, but doesn't seem to cause any problems.
Actually I was being serious. Though I was smashed at the time, so my wording probably wasn't the most clear. Basically what I'm saying is that bugs experienced from large mergers should be handled in house first, and only reported here after someone with some knowlegde has checked the crash with a debug dll, and concluded it's something in the RevDCM core, and not a problem with the mod itself. With RoM, you're the person who will be the most responsive to check up on crash reports, so really the report should be handled and by yourself. Personally I don't want LoR users coming in to the RevDCM forums and reporting bugs they encounter with LoR here, I'd rather check it first, and be sure it's not a problem with my changes first. Same goes for RoM.
Thanks very much for fixing this, I am due to start a new MP game this Sunday, so we will use the development version (unless you release a 'final' 0.82 before then)