Closed JFDaly closed 7 years ago
do not do it.
Just make sure you still have VS 2010 (or 2008) installed
I have both still installed.
When I click cancel, it brings up this:
This look better?
After the previous error, I selected a 'fix errors' option and then the project appeared in the solution explorer. After rebuilding, I got this output, which, although looking intimidating to me, reckons that it was successful.
picture link is broken if it is 56 errors, that is good.
Yea, dunno why they had to change imgur. Pic should be fixed now. That looks like 56 million errors, yea.
In 'error list' do you get o errors, 56 warnings?
Yeap
You are good to go, then.
Awesome, thank you for your help.
C++ easier than you think to read/work - you'd be a pro at it (as you are skilled with lua).
Very same concept(s), just slightly different vocabulary.
Civ VI might be an opportunity to get into it, yea.
Yeah, no need currently when you have me to write your code for you! :)
btw all latest requests from you worked, ja?
This is true :p
Yes, everything is working perfectly. I'm nearing the finishing stages of Sovereignty, so I don't think there's really anything more that I'd need, short of fixing anything that might be causing CTDs.
Sounds good.
Okay, so I got a CTD, but I'm not really sure where to find info about it. The old way of doing this had more info, that is, it would point to somewhere in the DLL where the crash occured (which often gave me some idea where in the lua/database the crash came from). But the call stack seems a lot less informative this time. Thoughts?
Did you build a new DLL and then put that in your CP folder in MODS? If not, do that. If you did, then this is a pure lua crash - not a lua crash as a result of a DLL pull.
Yea, I did. Hm, I'll have to comb the Lua then. Thanks.
Yeah, that's an unfortunate crash. Are you 'hooking in' VS to civ while it runs? Sometimes it grabs an error that the minidump misses.
By way of 'Attach to Process'? yea.
Yeah, that's the best way to test. You might also copy->paste the .pdb file from where the DLL is made into your CP folder. That's where 'symbols' are stored that let you read crashdumps.
I'll give it a shot. The CTD seems consistent from the turn that it last did it, and I previously did four tests without a CTD before I added ExCE onto the lot - so I should have somewhere to start.
Adding the pdb file didn't tell me anything more, unfortunately.
was afraid so - definitely a pure lua issue.
Good ol' ExCE is causing a CTD again, somewhere, but this time its impersistent. Could you please take a look at the MiniDump here and tell me if its decompiling to Lua or if its something else. Thanks.
This is with only ExCE, CP (12/03), and IGE.