Please, follow the Bug format for allowing us replicating the issue and fix it ASAP.
the format was taken by Nick and Published in the previous forums of BMS:
Effective Bug Reporting
An effective bug report communicates well with the BMS developers and avoids confusion or miscommunication.
Before you add a new bug report, please use the search function to check if the same bug has been reported or not. A good bug report should be clear and concise without any missing key points. Any lack of clarity leads to misunderstanding and slows down the development process as well. The most important point that you should keep in mind is not to use a commanding tone or harsh words in the report. This breaks the morale and creates an unhealthy work relationship. Use a suggestive tone. The import information that a bug report must communicate is:
Version and Build number
.cam, .tac, .twx, .ini, .vhs (ACMI), … if applicable depending on type of bug
The report should clearly answer how the test was performed and where the defect occurred exactly. The reader should easily reproduce the bug and find where the bug is. Hence it is best to split multiple issues into separate bugs. This ensures that each bug can be handled individually.
Always use KTO as your standard Theater of Operations and the current Vanilla installation without any further modifications!
If you discover a bug in another theater, please reproduce it in KTO as well. This can already exclude some sources of error.
It is very important to layout exactly what you did, in a step-by-step manner if necessary. Try to include all the information that you think would be helpful, but don’t be overly verbose. Now try to explain what happened the best you can. If you received an error message, it is always important to include the full, specific message. If you’re having trouble explaining it, pictures can be better than 1000 words. Use the attachment option whenever reasonable. Finally, try to explain what you expected to happen. This helps everyone understand what you were thinking and will often lead to improvements.
You can easily just copy and paste from this template: Version
<p>Hi, Snake. While this doesn’t help Amr much, perhaps I can help with your Amphib landing. What I did , via Mission Commander, was to add the Wasp ARG (put an AV-8B squadron on it[In some Theaters like Korea 2012 you also have the F-35 option]),and Newport ARG off the coast. Then I put my ground forces at the shoreline, set their waypoints, and off they went. <br /> I put the Newport in as the Wasp doesn’t land large tank forces The Newport LST’s are designed for that. They can each carry 29 tanks or 30 AAV’s, and each Newport ARG spawns with 2 Newports.<br /> BTW, bridge status wasn’t an issue in my case, but you are absolutely right that it can be a big factor. <br /> Hope that helps</p>
There is also a KOTAR-like bombing range in Mideast 128 theater, in the UAE just 20 miles south of Al Minhad airbase, though Mideast 128 theater conversion for use in BMS 4.36 is not yet complete (work is in progress to convert it).
<p>@zamcesarc <br />Thanks a lot, mate.<br /><br />After having seen what’s currently happening, should I say<em> “That’s the history, baby. And you can’t help it”,</em> then?<br /><br />With best regards.</p>
We could in case hope in that Central Europe that Falcas announced some time ago… but he is used to take his time to do things as he think they deserve to be done (his good right) and who may know, even he is awaiting the new terrain system to be released.