riddleofsteel
Office Linebacker
I myself haven't had a chance to try the fix. Tomorrow I should be able to.
Playtest Feedback Thread
- Thread starter The Capo
- Start date
AbsintheRed
Deity
Hm, now I'm out of ideas. Tried many things, and still can't get the 4th playtest to work
The user interface is still missing...
The user interface is still missing...
Missing user interface means there was a fatal python error, probably related to where or how you installed the mod. You'll need to enable logging (in CivilizationIV.ini) and see what Logs/PythonErr.log says.
If deleting that file isn't working for you then that means you've not installed the mod in a standard place (or something is not set right in Windows Vista/7) and you'll instead need to edit that file and add the path you're using. There's a copy of it in NewMod/Info.
If deleting that file isn't working for you then that means you've not installed the mod in a standard place (or something is not set right in Windows Vista/7) and you'll instead need to edit that file and add the path you're using. There's a copy of it in NewMod/Info.
AbsintheRed
Deity
Where and how I installed is the same as before
I tried many modular settings and other things to solve this, but don't have any clue what's behind this
I will try the python log soon, hopefully it will help
I tried many modular settings and other things to solve this, but don't have any clue what's behind this
I will try the python log soon, hopefully it will help
AbsintheRed
Deity
you meant this line in the .ini right?
; Set to 1 for no python exception popups
HidePythonExceptions = 0
I did not find anything directly to enable logging, just this setting which enables popups
; Set to 1 for no python exception popups
HidePythonExceptions = 0
I did not find anything directly to enable logging, just this setting which enables popups
Nope it's this line:
Code:
; Enable the logging system
LoggingEnabled = 1It should be near the end of the file, 6th to last on my system.
AbsintheRed
Deity
Thanks, found it
I will test it out tonight
I will test it out tonight
The Capo
godless Heathen
I seem to be getting some MAF errors now where I wasn't getting them before. I am thinking that the errors have something to do with the Flavian Amphitheatre. The reason I think this is because whenever I don't have the wonder (and the AI does) there seem to be MAFs occuring, and when I build it I don't see any.
Is anyone experiencing something similar, or just MAFs in general?
Is anyone experiencing something similar, or just MAFs in general?
The Almighty dF
Pharaoh
I've only gotten a couple, but in the expected areas. Mainly just when a large amount of units are active at once.
It should be noted though that I tend to play with 10 civs on standard sized maps, or 12 civs on large maps at Marathon speed. I know some players prefer to go the full 18 civs, but I've found that Civ4 tends to not be that stable once you pass 16 leaders at once.
I'll try out the Flavian Amphitheater thing if I can. The AI has yet to actually build it in any of my games (and I never build it because I'm never going against an AI where it'd be useful.)
The Capo
godless Heathen
Well here is the thing. I play this mod constantly as I work on it. So when I say that I did not get this many MAFs it means I saw the progress (or what should have been the progress) towards MAFs occuring.
The thing about this, is that it didn't start occuring until I played the playtest. So up until that point, there were no MAFs. And I mean NONE, the entire time. So this is throwing up some type of red flag to me. I am pretty sure it wasn't until I got the Flavian Amphitheatre to work that the MAFs started. So I'm thinking that it might be an issue. If I find that it (or another wonder, perhaps Machu Picchu) is creating MAF issues how should I proceed?
Should I remove it out of hand, or what?
The thing about this, is that it didn't start occuring until I played the playtest. So up until that point, there were no MAFs. And I mean NONE, the entire time. So this is throwing up some type of red flag to me. I am pretty sure it wasn't until I got the Flavian Amphitheatre to work that the MAFs started. So I'm thinking that it might be an issue. If I find that it (or another wonder, perhaps Machu Picchu) is creating MAF issues how should I proceed?
Should I remove it out of hand, or what?
The Almighty dF
Pharaoh
I wouldn't remove it since it's still a major wonder. I'd give the Flavian a more traditional bonus, like an extra trade route and some extra happiness.
I doubt it's Machu Pichu, because that's been in -all- of my games thus far, because I prioritize that thing (the random map generator hates me, so I always have a city that gets stuck near some cliffs just so I can get x resource.)
The Capo
godless Heathen
I don't know exactly how I'll figure this out, but I'll try to figure out if it is the Flavian Amphitheatre that is giving me problems, if so I wouldn't be entirely against removing it. For one it is kind of expensive for a small, albeit awesome, feature. Secondly, I think it slows the game down a bit (it has to fire every time a unit is built I believe), so I'll keep testing it out, but I might be leaning towards removing the Flavian Amphithteatre. 
I had a quick look through some of the Python you've added. It seems you've re-enabled 3 python callbacks that are off by default (because they slow down the game):
USE_CANNOT_CONSTRUCT_CALLBACK
USE_CAN_BUILD_CALLBACK
USE_ON_UNIT_CREATED_CALLBACK
I'd suggest temporarily disabling them to see how much speed difference it makes. I'm assuming that the Flavian Amphitheatre uses these, does anything else? These Python callbacks should really only be enabled for major features, especially the first two.
I also wouldn't be surprised if the slavery code is a part of the issue. It's called every single time there is combat, whenever a city changes owner, and every time a city updates it's production.
USE_CANNOT_CONSTRUCT_CALLBACK
USE_CAN_BUILD_CALLBACK
USE_ON_UNIT_CREATED_CALLBACK
I'd suggest temporarily disabling them to see how much speed difference it makes. I'm assuming that the Flavian Amphitheatre uses these, does anything else? These Python callbacks should really only be enabled for major features, especially the first two.
I also wouldn't be surprised if the slavery code is a part of the issue. It's called every single time there is combat, whenever a city changes owner, and every time a city updates it's production.
The Capo
godless Heathen
I'm pretty sure these are all used. How can I check for sure though?
The Capo
godless Heathen
I guess more specifically, how do I know if I can turn it off, and what parts of code they are attached to?
They're all in Assets/XML/PythonCallbackDefines.xml. The ones set to 1 are enabled, the ones set to 0 are not. Switching them off shouldn't cause any errors, just several sections of pythons won't ever get run. I'm not quite sure which sections these are without a more thorough examination of everything you've added.
I haven't got time to properly test it myself atm but switching these off temporarily should give some indication of how much speed could be recovered without having to comment out huge sections of python.
EDIT: Would be worth looking at the Next War compilation you used originally, see if any of these callbacks were enabled for that or if all were enabled subsequently.
EDIT2: Just saw your PM. I'm a bit busy this weekend but I'll have a look through and see if I can figure out what uses what.
Actually it looks like it's much easier than I expected to work out what uses which callback. Here's the list:
USE_CANNOT_CONSTRUCT_CALLBACK
- Used by Next War for arcologies and shielding
- Used by Machu Picchu
And unless I'm misunderstanding something it looks like USE_CAN_BUILD_CALLBACK and USE_ON_UNIT_CREATED_CALLBACK are not used by anything at all! Definitely switch these two off and hopefully that will see a decent speed increase.
USE_CANNOT_CONSTRUCT_CALLBACK
- Used by Next War for arcologies and shielding
- Used by Machu Picchu
And unless I'm misunderstanding something it looks like USE_CAN_BUILD_CALLBACK and USE_ON_UNIT_CREATED_CALLBACK are not used by anything at all! Definitely switch these two off and hopefully that will see a decent speed increase.
avain
(key)
Hi!
Assert Failed
File: CvArtFileMgr.cpp
Line: 179
Expression: false
Message: get##name##ArtInfo: ART_DEF_IMPROVEMENT_CITY_RUINS_ARCOLOGY was not found
Assert Failed
File: CvArtFileMgr.cpp
Line: 179
Expression: false
Message: get##name##ArtInfo: ART_DEF_IMPROVEMENT_CITY_RUINS_ARCOLOGY was not found
avain
(key)
The Babylonian Paratrooper is missing it's backpack texture.
Capo put out a patch for the playtest that fixed these and a few other things. It's somewhere in this thread I think.
