The standard approach is to make only one change at a time to isolate the issue.

Quote from: vonfrank on May 11, 2024, 03:36:07 PMI figured it was something like this...

Any ya, that sounds difficult to specifically narrow down and fix. It would likely require somehow determining the specific file causing the crash. I guess there's no console or error logger to figure this out?

Unfortuntately not for multiplayer.

Quote from: Dark_Phantom on May 11, 2024, 08:27:16 AMSounds like a memory issue with the specific hero you're using.

MP has much more stringent limits than SP to better facilitate online play.  It leaves a lot of maps by someone like Sereja without an immediate solution for online play.

You'll have to either swap out or rebuild the hero so that it is compatible.  It looks to me that it is probably a mesh or animation issue because it waits until they spawn into the game to crash.  What exactly that would entail to fix, I'm not sure.  There are minute differences in the BF2 skins that do cause issues in BF1 I believe but in SP the game usually compensates for them.

I figured it was something like this...

Any ya, that sounds difficult to specifically narrow down and fix. It would likely require somehow determining the specific file causing the crash. I guess there's no console or error logger to figure this out?

Also, there are some BF2 units like the ones with animated dreads that are not supported in SWBF1.

Quote from: Giftheck on May 08, 2024, 02:08:33 PMFor SWBF2, the LUA format is unchanged, so you should be able to change and munge a new mission.lvl.

Oh ok, I edited the script for felucia to change boba to vader, then used visual munge to compile it. It says it copied these things to battle front 2's folders but nothing is there. I'm not exactly sure I understand the steps I'm supposed to take.

Sounds like a memory issue with the specific hero you're using.

MP has much more stringent limits than SP to better facilitate online play.  It leaves a lot of maps by someone like Sereja without an immediate solution for online play.

You'll have to either swap out or rebuild the hero so that it is compatible.  It looks to me that it is probably a mesh or animation issue because it waits until they spawn into the game to crash.  What exactly that would entail to fix, I'm not sure.  There are minute differences in the BF2 skins that do cause issues in BF1 I believe but in SP the game usually compensates for them.

The PC spawn screen was farmed out to a third-party.  It was coded to be more refined for PC users but in the process they only allocated 5 slots for everything on the screen because they only had 5 units for each team on every map at the time - one of the few situations where modding has been hampered on the PC version.

Thanks you very much for those Reply ! that sad to hears    

I guess only console and "Classic" (that strange, but i guess their a reason behind it, smth to do about memory i guess?), that would be able to get more mods class restored, that can be a reason to buy it for that.

more mods lost to time _[T |°|]_

Quote from: Giftheck on May 10, 2024, 01:36:04 AMSounds like a client/host mismatch. If you have heroes in your script that aren't present in the scripts of other players in the match, it'll crash.

Unfortunately, it's not that simple. For 2 reasons.

1: The person I've tested this with has a literal copy-pasted mod install to my own. It is 100% identical.

2: It crashes my own client even when hosting an MP match with no one else but myself present. So it can't be due to a mismatch since I'm the only player in those tests.

Sounds like a client/host mismatch. If you have heroes in your script that aren't present in the scripts of other players in the match, it'll crash.