Bridge Commander Central
BC Forums => BC Scripting => Topic started by: NatsuKagura on January 21, 2011, 10:51:20 PM
-
hi Guys, since two weeks ago I have been wondering about it:
-The subsystem damage indicator on the tactical display. :lostit:
I have tried to modify weapons hardpoint via Tactical Display Editor (TDE), but for some reason even after I edited & recompile the HP, it crash during the game. :banghead: So I copy & replace the Icon & indicator, one by one, to my original Hardpoint.py & it's work. :D
Then I try to edit her damage indicator for each of her subsystem, it's okay until I finished editing it with TDE.
However, when I try to copy & paste it to my original Hardpoint.py ,I can't found the script line for the damaged subsystem icon on the hardpoint.py. :lostit:
Could anybody point me out, which is the line on the hardpoint.py to modify the damage indicator icon for each subsystem? :bow:
Thanks guys.... :thumbsup:
-
Try using this program (http://bcs-tng.com/portal/?q=tacdisplayiconeditor) it's a replacement for TDE and doesn't require you to decompyle or recompyle hps only load and save changes.
-
everytime you paste modified .py file into
ANY scripts subfolder make sure you deleted it's .pyc version ;)
-
everytime you paste modified .py file into ANY scripts subfolder make sure you deleted it's .pyc version ;)
Why?
-
BC has a habit at least that I noticed that it still uses the pyc even though a new py is there. (this isn't related to OS)
-
BC has a habit at least that I noticed that it still uses the pyc even though a new py is there. (this isn't related to OS)
I'm aware that people believe this and was expecting such a reply, but I decided to wait and see.
No, the observation is wrong. BC will compile py into pyc when it's required with or without an existing pyc.
-
Thanks Sovy, Bones, Nebula..... :D :D :D
wow, that's different with the one I used... thank you Sovy.... :thumbsup: cookies... nyam...nyam...
Now I can make the damage icon properly.... ;) ....
-
I'm aware that people believe this and was expecting such a reply, but I decided to wait and see.
No, the observation is wrong. BC will compile py into pyc when it's required with or without an existing pyc.
oh, I always thought old .pyc were getting in the way of new .py, had a situation while rehardpointing a ship when BC crashed due to having old pyc and modified py, at least I guess that was the problem because when I dumped .pyc everything worked properly :idk:
-
No, the observation is wrong. BC will compile py into pyc when it's required with or without an existing pyc.
rly? wow then!
but then what's with hp files still showing characteristics of the old hp when one replaces the py without deleting the pyc?
this is what's confusing me here.
-
in the past a few times i did notice what neb is describing, where i would alter a py and not notice the new changes ingame until i exit bc and delete the pyc... then the changes i did make would occur...
tho for me, it wasnt hp pycs... in fact, i never delete hp pycs and always notice the new changes... it was other scripts, tho i cant recall exactly which ones and when... and, it seemed a very rare event for me (literally only a few times in all the years) as i usually never bother deleting pycs; tho i do advise to others that it be a good habit to get into...
-
If someone edits scripts while the game is still active this requires you to reload the scripts which are currently loaded, for the changes to be reflected. Otherwise you will not have problems; if you Exit BC, edit scripts and re-enter the game. This is what I recommend. BC will also not compile scripts if there is an error in the py file.
In 9 years since I've had BC I've never observed the behavior you're describing and I've never deleted a single pyc, unless I wanted to get rid of a mod that is.
BC might have problems if you supply only pyc's to it as was sometimes case, so it's recommended to supply py's instead.
-
I never edit or replace scripts while BC is running.
-
BC will also not compile scripts if there is an error in the py file. Mixed with other script error.