<p>In the Login page of the Bugtracker I see the following warning:<br /><br />>>><br />Warning: “admin” directory should be removed, or access to it restricted.<br /><<<<br /><br />To which “admin” directory is this refering to ?<br />To the “admin” directory on my local PC ?<br /><br />Thanx<br />Sunnny</p>
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
My bad, nvm, figured it out , didn’t read properly. OP is talking about INS/GPS weapon , not related to… HMD.
But, afaik that amount of error “could be” viable for , about ~60mins in the flight for the plane’s INS system … (speaking from memory)
Actually , have you aligned weapon’s GPS properly … to A01 ?
Yesterday I dropped 4 Jsow-a’s from max distance (via TGP only, no radar, no laser) and scored good… well, partially good , since first 2 in tandem side-by-side , seems one missed … meh , haven’t record avtr so can’t confirm.
But 3 and 4 fired independently hit fine.
I’ve had 2x STA errors from all that ACM (had to evade AA12)… so maybe one AGM was MAL … still fired … and 1 Aim120 got hung (hmm not in fault list below) … right when was needed … I don’t like that “new feature” at all 🙂
… I know it’s not exactly “pinpoint” gps weapon , but still from max range…
Wingman droppped 8xSDB’s … and all hit, but that’s AI.
I will try next time with something like SDB … and STP only.
This mission was hairy… all other package elements got shot down, me and my AI wingman survived and come back , Rambo style 😄
@Mav-jp Awesome, thanks a lot.
You just made my day…twice.
First because of this great addition.
Second because you might have edited your post. Here is the text I received in my mailbox from your post:
“I cooked a fox for this”
Now I know BMS coding is sometimes like voodoo magic, but I just thought it was a bit extreme …
[BMS4.36] The nm range setting for the Wonju AB Tacan channel 060Y in the “Station+Ils.dat” file (Falcon BMS4.36/Data/Campaign folder) is set to “0” instead of “40” (reference KTO_AIP.pdf), therefore, cannot receive Tacan 060Y range info unless edit Station+Ils.dat file to change 0 to 40.
Secondly, it appears that the Wonju AB Tacan channel 060Y and Vortac channel 039X should be reversed in the Approach Charts when compared to “Station+Ils.dat” file and KTO_AIP.pdf.
Hi, thanx for posting.
It’s a known issue, related somehow (apparently) to some 3D models and will not be fixed for 4.36. The problem doesn’t exist in the Dev/Coming-next-someday 4.37 version due to changes elsewhere in the sim’s code and DB. I decided to not try to chase it as only some vehicles are affected and only BHOT apparently.
@Starkes So my connection issues was due to editing the hot fix with Excel instead of notepad, which caused my falcon BMS CFG file to get corrupted with random Quotation marks all throughout random lines in my BMS CFG file. I basically copied and pasted a new CFG file from a friend and then correctly placed and edited the hot fix and then everything worked fine.
It is quite refreshing. Seems like now hostiles crank, create grinders, flow cold around pitbull. They are more human like and its nice to have a challenge rather than them to keep pushing and getting shot down every time.
Thank you, guys. I really appreciate your timely response. I was a little unsettled about Falcas Mission Commander not working anymore. However, you were exactly right about the Editor being able to resupply the squadron supplies, drtbkj.