The original coded limit was 12.  Assuming they use the console code, that would be the limit.

The people that Pandemic farmed the PC spawn screen out made it only support 5 because that was what was on every map.

If you break the PC Spawn Select as I've noted maybe in the Tutorials section (requires hex editing the exe), you can have up to the original designed limit of 12 with various issues that come from poor memory allocations on the screen.

I got it munged but not in a way ZE can read it - only ingame.  It didn't crash after a long time of running it but I was really trying to find the source of the crash.

Hey Metalkiller! This is a great project. I doubt I have implemented anywhere near as much as you but if there's anything you can glean from my bad implementation of bytecode parsing, go ahead:
https://github.com/phantom567459/BF1LuaDC/blob/master/LuaDC1/Program.cs

I'll take a look in the near future and see if I can get some of the more obscure implementations documented and maybe fork your code instead to go further back in the process. I thought I tried Lua4Dec at one point but maybe I need to try again.  I know my project is a little bit different but tries to target the bytecode more directly for BF1

Thanks!

Hmm, very weird. If I get some time tomorrow evening I'll toy with jt.

Another option, as long as you're not using foliage, is to use BF2's munger (TerrainMunge.exe) to munge the terrain for BF1.  It sounds crazy but the BF2 version is actually not different from the first one except for foliage optimizations so you should be able to compile the original terrain file without hex editing.
(To do this quickly, rename your TerrainMunge in ToolsFL, put BF2's TerrainMunge in there, clean and munge your project.  After the project is done, you may want to swap it back because of foliage support.)

Yeah as far as I know the only way to host a dedicated server is to have a physical Xbox (or possibly XEMU on your PC) to run a full version of the game and press the button in options when creating a game to run a dedicated server.
There is no specific software for it because it used Xbox Live, not Gamespy.

I'm going to recommend you look at other projects first before digging too far into your quest.  LibSWBF2 is a good way to start.  For sounds and cutscenes, I have a project called SoundFMVExtractor that can rip out all sounds and cutscenes from both games.  Both are hosted on Github.

The reason there's dependencies on DirectX is the fact that the images are compiled in a DX compatible format.  It shouldn't dissuade you since there's plenty of resources but just making sure you know why.

And just to be pedantic, SWBF1 and 2 are NOT the same engine as previous Pandemic games, despite popular belief.  The same style is there but a lot of it was written anew for the BF games, and mungers were used to convert from the old MSH (TCW and others) format to the new SWBF compatible formats.  Also some of the same people working on it and some reused libraries mean there are similarities but they aren't the same.

Good luck!

Basically here we can see that end_weap_tripwire does work in the retail game.  The only thing that is needed is to make sure you have the tripwire asset from the END world folder, and also the animation files (zafbin/zaabin).

You will need to edit the end_weap_tripwire.msh file in XSI or Blender to remove the collision that has been set up - it seems that breaks it in the retail version (only... strangely enough).  The munger will generate the correct collision.

That's it!  I wish the trap class got more usage in mods but 20 years later, it's probably too little, too late.

A side note: Units and vehicles both DO trigger traps.  The difference seems to be the RayTriggerMinSpeed modifier.  The only other traps in the game are the tree smashers on Endor and the also unused log trap.

Quote from: AnthonyBF2 on October 23, 2023, 06:00:12 PMCan you tell me more about this? Is the limit higher on Steam? Is the limit based on missions or total addons?

Steams is 512 iirc

BF1 1.2's (disk/dvd version) limit for mod map instances is 50.  Mostly we just say 20 because if you have 25 with 2 eras each, then you'll be at the limit (this includes TAT3).

The actual technical reason is that the array isn't big enough and once you hit 50 it just keeps writing over the last entry.  I'm not good enough at assembler to get a bigger spot in memory for it.

Wine is a fickle beast and whoever created the wrapper probably didn't test every option for BF1.  I've only tested all those flags on Windows.

If it's for the main game, you need a Core.lvl Tool that can compile for the main game.

If it's for a custom map, BFBuilder has an edit_localization batch that should suit.  You just need to find the key for cis_inf_super_battledroid (or whatever that odf is)

I was requested to update the Side Builders and here they are. Everything should already be set up for 1.2 and this also includes munging for the side FPMs which I don't believe has been included before.

The munger does every side, please read the readme on how to disable one side from being munged.

Long live BF1!

http://www.swbfgamers.com/index.php?action=downloads;sa=view;down=1621

http://www.swbfgamers.com/index.php?topic=13659.msg122080#msg122080

Rather than recreating, just import the stock maps and then use ZE to modify them.
Please make sure to read the download notes first, they answer very common questions.

The answer is simpler than you're making it out to be.

The easiest way I believe would be to remove imp_droid_probe from the stock Hoth mission.  Searching "mission.lvl builder" should bring it up.  The one on the site is reasonably easy to use and would allow you to use the stock Hoth level.  It'd probably break online compatibility.
The other answer that nobody has really gotten to is to figure out why it's crashing.  I see the REQs listed correctly but the devs might have used a different model that's compatible with the game, or something else.

There are SWBF2 map conversions on here but that's not the correct answer to the problem you're experiencing and adding a whole other level of complexity.

Happy New Year!