Python Performance and Interface Overhaul (PPIO)

Is it possible to manually add buildings to the "hidden" list (that normaly only lists unconstructable buildings)?
Tricky at best... Probably possible, but not something I'm willing to work on atm.

▬▬ Edit: ▬▬▬▬
v0.5.9.1.1
  • Technical performance and bugfix update.
▬▬ Edit: ▬▬▬▬
v0.5.9.1.2
  • Technical performance and bugfix update.
▬▬ Edit: ▬▬▬▬
v0.5.9.1.3

  • Technical performance and bugfix update.
 
I am in the recent SVN 9772 and interface overhaul modmod v0.5.9.1.2. I still I cannot see the properties (crime, disease etc.) of the cities.

I have managed to change the setting in %USER%\Documents\My Games\Beyond the Sword\CivilizationIV.ini but there is nothing related to python in BUG options. There are only screen and file logging levels. To be 100% sure, you are referring to the menu one can access with alt+ctrl+o when he is in the middle of a game. Right?
 
I am in the recent SVN 9772 and interface overhaul modmod v0.5.9.1.2. I still I cannot see the properties (crime, disease etc.) of the cities.

I have managed to change the setting in %USER%\Documents\My Games\Beyond the Sword\CivilizationIV.ini but there is nothing related to python in BUG options. There are only screen and file logging levels. To be 100% sure, you are referring to the menu one can access with alt+ctrl+o when he is in the middle of a game. Right?

I think I have managed. I see a lot of python exception messages at the end of every turn. But what is the path of the log file. I couldn't find it.
 
I think I have managed. I see a lot of python exception messages at the end of every turn. But what is the path of the log file. I couldn't find it.

Log files should be in %USER%\Documents\My Games\Beyond the Sword\Logs.

PythonErr.Log contains the actual Python error messages and is essential to figuring out where something goes wrong in Python

PythonErr2.log and PythonDbg.log contain "trace prints". Things put in by various modders to check that things are going fine and have the correct values. They is not of great use in debugging a problem but do have a lot of interesting stuff in them.​

These log files will be overwritten at the beginning of a game session.
 
I think I have managed. I see a lot of python exception messages at the end of every turn. But what is the path of the log file. I couldn't find it.
There should be a shortcut in the top folder of the mod called logs, it should in principle work for all kinds of BtS installations. Do try the latest version of the modmod before posting any pythonErr.log files, I might have fixed it by coincidence. I've not managed to get the same bug as you reported in my games, so I can't fix it without that log file.
Thanks for making an effort. ^^
 
Hello, I started a new play with latest C2C build (9773) and this modmod (0.5.9.3) and I'm getting this errors every turn
6pmbki.png

Also, in city window, no properties or resources showing.
 
Hello, I started a new play with latest C2C build (9773) and this modmod (0.5.9.3) and I'm getting this errors every turn
6pmbki.png

Also, in city window, no properties or resources showing.
Do you have your system setup to treat you as the administrator?
 
Just making sure. I know some of those are specific known bugs at the moment but the long list of py errors I hadn't seen reported yet and it looks like that when a player hasn't been running as an administrator.
 
v0.5.9.1.4
  • Bugfix update.
  • After a lot of borked versions, I'm finally crossing my fingers that this version is stable.
    • Sorry for the instability lately guys/gals.
 
Thanks, I got no errors messages now, but Properties in city windows still not showing :(
 
I couldn't say, this is the content of PythonErr2.log


Spoiler :
load_module CvEventInterface
load_module BugEventManager
load_module CvEventManager
load_module CvUtil
load_module traceback
load_module CvScreensInterface
load_module CvMainInterface
load_module operator
load_module string
load_module time
load_module ScreenInput
load_module CvScreenEnums
load_module ProcessUpgrades
load_module BugUtil
load_module BugPath
load_module BugConfigTracker
load_module ColorUtil
load_module Immigration
load_module PyHelpers
load_module AbandonCityEventManager
load_module CvMADNukesManager
load_module Popup
load_module math
load_module BugDll
load_module BugOptions
load_module BugConfig
load_module BugCore
load_module BugInit
load_module BugTypes
load_module xmllib
..\WARLORDS\ASSETS\PYTHON\SYSTEM\xmllib.py:9: DeprecationWarning: The xmllib module is obsolete. Use xml.sax instead.
20:46:24 DEBUG: BugConfig - registering xml handler BugConfig.RootHandler
20:46:24 DEBUG: BugConfig - registering bug handler BugConfig.BugHandler
20:46:24 DEBUG: BugConfig - registering load handler BugConfig.LoadHandler
20:46:24 DEBUG: BugConfig - registering config handler BugConfig.ConfigHandler
20:46:24 DEBUG: BugConfig - registering arg handler BugConfig.ArgHandler
load_module configobj
load_module __future__
load_module codecs
load_module validate
validate import failed
load_module RevInstances
load_module BugOptionsScreen
load_module BugErrorOptionsTab
load_module BugOptionsTab
load_module BugHelp
20:46:24 INFO : BugCore - creating uninitialized mod Core
20:46:24 INFO : BugCore - creating uninitialized mod MainInterface
load_module MonkeyTools
20:46:24 INFO : BugCore - creating uninitialized mod NJAGC
20:46:24 INFO : BugCore - creating uninitialized mod Scores
20:46:24 INFO : BugCore - creating uninitialized mod CityScreen
20:46:24 INFO : BugCore - creating uninitialized mod Revolution
load_module Scoreboard
load_module DealUtil
load_module PlayerUtil
load_module TradeUtil
load_module DiplomacyUtil
load_module AttitudeUtil
load_module FontUtil
load_module GameUtil
load_module BugUnitPlot
load_module UnitUtil
load_module ReminderEventManager
load_module SdToolKit
load_module BugData
load_module cPickle
load_module autolog
load_module CvModName
20:46:24 INFO : BugCore - creating uninitialized mod Autolog
20:46:24 INFO : BugCore - creating uninitialized mod Reminder
load_module CvAppInterface
load_module GPUtil
load_module ProgressBarUtil
load_module RawYields
load_module CvTechChooser
load_module PlatyOptions
load_module CvForeignAdvisor
load_module CvExoticForeignAdvisor
load_module IconGrid_BUG
load_module DomPyHelpers
load_module TechTree
load_module FavoriteCivicDetector
20:46:24 INFO : BugCore - creating uninitialized mod Advisors
load_module CvReligionScreen
load_module ReligionUtil
load_module CvCorporationScreen
load_module CvCivicsScreen
load_module CvVictoryScreen
load_module TechUtil
load_module GameSetUpCheck
load_module AutoSave
load_module MapFinder
load_module MapFinderStatusScreen
20:46:24 INFO : BugCore - creating uninitialized mod MapFinder
20:46:24 INFO : BugCore - creating uninitialized mod AutoSave
load_module Buffy
20:46:24 INFO : BugCore - creating uninitialized mod BUFFY
load_module CvEspionageAdvisor
load_module SpyUtil
load_module BugScreen
20:46:24 INFO : BugCore - creating uninitialized mod BetterEspionage
load_module CvOptionsScreen
load_module CvReplayScreen
load_module CvHallOfFameScreen
load_module CvDanQuayle
load_module CvGameUtils
load_module CvUnVictoryScreen
load_module CvDawnOfMan
load_module CvTechSplashScreen
load_module CvTopCivs
load_module random
load_module CvInfoScreen
load_module CvIntroMovieScreen
load_module CvVictoryMovieScreen
load_module CvWonderMovieScreen
load_module CvEraMovieScreen
load_module CvSpaceShipScreen
load_module CvWorldBuilderScreen
load_module CvDebugTools
load_module CvDebugInfoScreen
load_module CvMapGeneratorUtil
load_module NaturalWonders
load_module CvGFCScreen
load_module BuildListScreen
load_module CvPopupInterface
load_module PediaMain
load_module SevoPediaTech
load_module SevoPediaUnit
load_module SevoScreenEnums
load_module SevoPediaHero
load_module SevoPediaRoute
load_module SevoPediaBuilding
load_module SevoPediaPromotion
load_module SevoPediaUnitChart
load_module SevoPediaBonus
load_module SevoPediaTerrain
load_module SevoPediaFeature
load_module SevoPediaImprovement
load_module SevoPediaCivic
load_module SevoPediaCivilization
load_module SevoPediaLeader
load_module SevoPediaTrait
load_module TraitUtil
load_module SevoPediaSpecialist
load_module SevoPediaProject
load_module SevoPediaReligion
load_module SevoPediaCorporation
load_module SevoPediaIndex
load_module SevoPediaBuild
load_module UnitUpgradesGraph
20:46:25 INFO : BugCore - creating uninitialized mod CustDomAdv
20:46:25 INFO : BugCore - creating uninitialized mod TechWindow
load_module C2CMainOptions
load_module C2CNationAdvisor
load_module Forgetful
load_module TimeKeeper
init-ing world builder screen
load_module CvDotMapOverlayScreen
load_module CvStrategyOverlay
20:46:25 INFO : BugCore - creating uninitialized mod StrategyOverlay
load_module CvCameraControls
load_module CvAdvisorUtils
Script pass None
load_module InputUtil
20:46:25 DEBUG: BugEventManager - adding event 'BeginActivePlayerTurn'
20:46:25 DEBUG: BugEventManager - adding event 'SwitchHotSeatPlayer'
20:46:25 DEBUG: BugEventManager - adding event 'LanguageChanged'
20:46:25 DEBUG: BugEventManager - adding event 'ResolutionChanged'
20:46:25 DEBUG: BugEventManager - adding event 'PythonReloaded'
20:46:25 DEBUG: BugEventManager - adding event 'unitUpgraded'
20:46:25 DEBUG: BugEventManager - adding event 'unitCaptured'
20:46:25 DEBUG: BugEventManager - adding event 'combatWithdrawal'
20:46:25 DEBUG: BugEventManager - adding event 'combatRetreat'
20:46:25 DEBUG: BugEventManager - adding event 'combatLogCollateral'
20:46:25 DEBUG: BugEventManager - adding event 'combatLogFlanking'
20:46:25 DEBUG: BugEventManager - adding event 'playerRevolution'
20:46:25 DEBUG: BugEventManager - adding event 'addTeam'
20:46:25 DEBUG: BugInit - init() called
20:46:25 DEBUG: BugInit - game not fully initialized
 
Last edited:
I ask myself over and over why do people post PythonErr2.log when asked for PythonErr.log?

In general PythonErr2.log is no use at all when trying to find any problem. As far as I can see it is only useful to the BUG modders. Perhaps we should look at turning it off.
 
I couldn't say, this is the content of PythonErr2.log
The PythonErr2 log has never been useful to me, so you can delete that part of your post, or at least put it in a spoiler.
There is some information on how to turn on python error logging in the opening post spoiler of this thread.

I've made some changes to the BUG options available for the city screen, could you try deleting your "BUG City Screen.ini" from the "Caveman2Cosmos\UserSettings" folder?
It might fix the issue you are having.
Perhaps we should look at turning it off.
I can look into it.
 
I deleted BUG City Screen.ini and I have enabled python exceptions on civilization IV.ini. Properties tab not working. I have some python exceptions on screen, but I don't have any pythonErr.log or pythonDbg.log on my entire system, only PythonErr2.log on logs folder. I'm writting manually the python exceptions I'm getting:

  • Attribute error: BugEventManager instance has no attribute 'TECH_COLONIALISM'
  • File 'CvEventManager', line 1808, in onCitybuilt
  • File 'BugEventManager', line 361, in _handleDefaultEvent
  • Traceback (most recent call last):
I'm getting 7x each of this four Python exceptions notifications
 
Last edited:
I deleted BUG City Screen.ini and I have enabled python exceptions on civilization IV.ini. Properties tab not working. I have some python exceptions on screen, but I don't have any pythonErr.log or pythonDbg.log on my entire system, only PythonErr2.log on logs folder. I'm writting manually the python exceptions I'm getting:

  • Attribute error: BugEventManager instance has no attribute 'TECH_COLONIALISM'
  • File 'CvEventManager', line 1808, in onCitybuilt
  • File 'BugEventManager', line 361, in _handleDefaultEvent
  • Traceback (most recent call last):
I'm getting 7x each of this four Python exceptions notifications
I must have forgotten to add an important file that I've been modifying lately.... which one could it be.
I'll keep digging, at least I have a concrete error to evaluate now.
 
Last edited:
Back
Top Bottom