@sheref Uh!!.. for laptops sound hardware… God only knows.
I was speaking about real sound-cards , not onboard audio chips …
Only way to find out is to test yourself.
!!!BUT!, really don’t forget, if you adjust that setting , and make your theater shared with others. - others WILL have that 32 sounds limit by default … as per BMS default.
…so experiences may really differ … I was merely speaking for testing purposes to see if number of simultaneous channels is giving you a headache , so test
…and also, since we’re in 21st , probably sound hardware is mature enough for BMS to lift that one setting at least to 63/64… need testing by other people first to see if it works sytemwide, on all hardware
Current status: The next issue is somewhere in here:
That’s the section of the units file for a flight. It has changed since 4.35 somehow. The numbers in that picture are pretty much all I have to go on. If I’m being honest, I’m not sure I have the will to chase this down. Without any information about what has changed, it’s extremely difficult to derive what this means. I can look at Mission Commander and try to infer it from there, but after several hours of doing that, I’m none the wiser.
If anyone has an in with the BMS devs, five minutes from them will save me literally hours. All I need is to know what has changed in the layout of various files. It would take seconds of looking at the source code to determine that. Without that help, I think I may finally have run out of energy for maintaining VMT.
Is there any documentation at all for creating a new campaign? I’m also interested in looking into creating one rather than the work I’m having to do at the moment in managing campaign’s with Mission Commander. (Which normally imparts some instability into the campaign, making crashes more frequent and such.)
In \campaign directory each campaigns have a tri files. (save0.tri, save1.try, save2.tri) These contain the victory conditions which objectives have to be captured. The ID numbers are campaign IDs. You can check camp ID values with Tacedit. The tri files can be editet with any text editor. (Notepad, Wordpad, etc.) With Tacview you can check which save is which campaign you will see because of the ownership of objectives. As I can remember save0 = Rolling Fire, save2 = Iron Fortress, save1 = Tiger Spirit
LAU-129 and 16S210 are both legit pylons.
the 16S210 can only be used for carrying AIM-9s (not sure that 9x) where the 129 can carry AIM-9s and AIM-120.
therefore the 16S210 is being phased out on the USAF, however, it is still very commonly used in other airforces. so saying “it’s not realistic” is a bit harsh.
however, there are some inaccuracies in the way the two launchers are used. let’s hope it will big corrected to the next version. 😉