Page 1 of 1
Map is fine on my machine but crashes on others [Solved]
Posted: Tue Oct 20, 2009 6:49 pm
by jangoisbaddest
I just released my beta, and everyone is reporting immidiate crashes. My maps have exactly 1 Severity 3 error in each mode, and none of them cause crashes for me. The map, in each mode, runs smooth as silk on my machine. Never crashes. What the devil is going on?!
One of my testers reported that there were several Severity: 3 errors that indicated several weapons and units in my custom side couldn't find their associated geometry. But, as I said before...they show up just fine on my machine. No such errors exist on my computer.
Has anyone run into this problem? I don't understand how messed up my beta release is when all I did was right-click my ABC folder in the Addon directory and make an archive with 7-zip.
Re: Map is fine on my machine but crashes on others
Posted: Tue Oct 20, 2009 7:03 pm
by Maveritchell
Could be any number of things that cause a map to crash on one computer and not another, when in doubt always consider what can be different between two computers - number of missions, graphical settings, water tolerance - all those can affect crashes on different computers.
If they have errors that you do not, I'd suggest you do a manual clean and remunge and then look at your Bfront2.log file.
Re: Map is fine on my machine but crashes on others
Posted: Tue Oct 20, 2009 8:33 pm
by Fiodis
Just tested and got the same CTD. Here's something:
Code: Select all
Message Severity: 2
.\Source\Combo.cpp(3398)
Combo[126da200]::State[IDLE:c301cf93]::Transition: invalid state e1e901c0 mapped to IDLE
Message Severity: 3
.\Source\Weapon.cpp(2076)
Weapon "ksh_weap_gree_rifle" missing high res geometry "rep_1st_weap_inf_rifle"
Message Severity: 3
.\Source\Weapon.cpp(2044)
Weapon "ksh_weap_rep_z6" missing geometry "rep_weap_inf_chaingun"
Message Severity: 3
.\Source\Weapon.cpp(2076)
Weapon "ksh_weap_rep_z6" missing high res geometry "rep_weap_inf_chaingun"
Combo issue? Missing weapon geometries? Maybe first-persons don't cause too many CTDs (I've never left a first-person geometry blank myself, so I don't know for sure) but apparently ksh_weap_rep_z6 is missing
any geometry whatsoever, which can't be to good. That's probably the crashing thing there for Conquest CW.
Oh, also,
Code: Select all
Message Severity: 3
.\Source\EntityGeometry.cpp(619)
Entity "ksh_cis_mangnaguard" missing geometry "cis_inf_magnaguard"
Maveritchell once wrote:How's that soldier without geometry working out for you?
Re: Map is fine on my machine but crashes on others
Posted: Tue Oct 20, 2009 9:11 pm
by jangoisbaddest
Exactly my point. No such errors exist on any mode at all whatsoever on my computer. Why is there such a gargantuan discrepancy? I may be something of a n00b still, but I know better than to release a beta before checking it for crashes like these or Severity 3 errors. Nothing before, nothing now.
Mav, I tried a full clean and re-munge. There was no difference - my game did not crash in any mode, and my log had no indication of any geometry or combo errors.
This makes absolutely no sense to me.
Re: Map is fine on my machine but crashes on others
Posted: Tue Oct 20, 2009 9:17 pm
by Maveritchell
jangoisbaddest wrote:Exactly my point. No such errors exist on any mode at all whatsoever on my computer. Why is there such a gargantuan discrepancy?
I will guess that you don't have the 1.3 patch installed and the users testing your map do. I think in some of the updated sides, the mesh names are different for the models you're trying to load through .lua without including in your sides physically.
To load unit models appropriately regardless of whether your users have the 1.3 patch installed or not, include the referenced unit (and consequently the corresponding model) as a class parent instead of directly referencing the mesh name. For the weapons, make sure you actually include the .msh in your side.
The easiest solution is simply to add those meshes to the side you're loading from.
Re: Map is fine on my machine but crashes on others
Posted: Tue Oct 20, 2009 9:21 pm
by jangoisbaddest
Maveritchell wrote:jangoisbaddest wrote:Exactly my point. No such errors exist on any mode at all whatsoever on my computer. Why is there such a gargantuan discrepancy?
I will guess that you don't have the 1.3 patch installed and the users testing your map do. I think in some of the updated sides, the mesh names are different for the models you're trying to load through .lua without including in your sides physically.
To load unit models appropriately regardless of whether your users have the 1.3 patch installed or not, include the referenced unit (and consequently the corresponding model) as a class parent instead of directly referencing the mesh name. For the weapons, make sure you actually include the .msh in your side.
The easiest solution is simply to add those meshes to the side you're loading from.
That's a good guess, as I do not have the 1.3 patch installed. Thank you, Mav. I'll be installing this and then doing some more bugfixing. Seeing as how the map crashes, there is no telling how many more of these errors will crop up if I simply fix the ones already mentioned.
My apologies to those of you that have this broken Beta. I guess it's going to be a bit longer. ><
Re: Map is fine on my machine but crashes on others
Posted: Tue Oct 20, 2009 9:32 pm
by Maveritchell
jangoisbaddest wrote:Seeing as how the map crashes, there is no telling how many more of these errors will crop up if I simply fix the ones already mentioned.
If it's any consolation, there are unlikely to be more. If, as you said, it worked fine on your machine before, these are the only errors that will be added because of the 1.3 patch.
Re: Map is fine on my machine but crashes on others
Posted: Wed Oct 21, 2009 12:36 am
by jangoisbaddest
Maveritchell wrote:jangoisbaddest wrote:Seeing as how the map crashes, there is no telling how many more of these errors will crop up if I simply fix the ones already mentioned.
If it's any consolation, there are unlikely to be more. If, as you said, it worked fine on your machine before, these are the only errors that will be added because of the 1.3 patch.
And you were correct. As always. Thanks a million. You have earned yourself a prominent place in my "special thanks" section of the readme (whatever that's worth).
