RAZBAM_ELMO

Gentlemen, I apologize I'm getting here so late but I'd like to get this sorted quickly and rest assured this will be given highest priority. Is this still present in the latest OB patch from 23/09/2020? I am not experiencing it myself. If it is indeed still present please attach a new .trk file so I can bring it to the dev team asap.

Hi Pierre, can you confirm this is still present in the latest OB patch 23/09/2020? If so please attach a .trk file. Thanks.

Working as intended.

Hi JuanAJ, can you confirm this is still present in the latest OB patch 23/09/2020? If so please attach a .trk file. Thanks.

System is working as intended.

Hello JuanAJ, if you can confirm this still present in the latest update from 23/09/2020. If so, please attach a new .trk file thankyou.

Galinette, if you can confirm this still present in the latest update from 23/09/2020. If so, please attach a new .trk file i would need you to follow the same steps to be able to see if this is a bug we can fix or if its an ED fix thanks.

Hi Steph, if you can confirm this still present in the latest update from 23/09/2020. If so, please attach a new .trk file.

Hi Snappy, if you can confirm this still present in the latest update from 23/09/2020. If so, please attach a new .trk file

Hello Galinette, can you confirm this is still occurring in the latest OB patch 23/09/2020? If so please attach a new trk file

Hi Pierre, can you confirm this is still present in the latest OB update from 23/09/2020?

@deepdiver8055 are you still experiencing this bug after the changes you made?

fixed internally and will be present in the next OB update

Please post a trk file so we can look atthis further. It may also be that you need to invert your axis. Try that as well.

Post a trk file please

Guys if you have a bug other than the one mentioned here, please make a new bug report related to that issue. This sis simply to isolate the GBU drop CTD. Thanks

Glad you thought about it. Yes in the future we do want to change things which is why we opened up discussions, this was Moreno to describe what's happening in the interim. Its been reccomended to hold of on future project developments until the larger portions of current modules is finished and we agree. Just today I went through two pages of the Harrier bugs section and got things organized. In the coming days, I'll be able to tackle the mirage and 19. Mirage has minor fixes that need addressing before considered Fully Finished while the 19 really only requires FM tweaks and occasional support after large updates. Sad to see someone go but know that theres always room if you decide to reverse the decision. You know I'll be the first one in line to say welcome back. Sent from my SM-N960F using Tapatalk

yes that is expected as this file disables MGRS coords. READ op. We just want to see if this fix rectifies the bug so we can better isolate the issue

I wasn't sure if that was link to a video but seen now. My apologies. I have posted a fix in the main section for this to work, should be titled *ATTENTION* if the problem persists then there are instructions there on how to properly submitt information on the matter.

If it can be uploaded here, that way I know for my own sanity sake which trks go where and I dont have to try and connect several posts together. Also helps differentiate the issues, and is more organized so I can go through all of the reports more easily and quickly.

Seen, tracking internally.

team is made aware, will update if info becomes avail.

Tag me when you have so I can update the status for the team and have them look at it with resources.

Look for your log folder in your saved games DCS folder of the .log and upload that then

Alright now that I have your attention everyone, the issue we have seen this morning with the CTD on GBU drops. The team has been very hard at work trying to get this bug sorted from when it began this morning. The team has a request for those experiencing the problem. Now because it seems to be a 50/ 50 split on who is or who is not experiencing the problem, we have a short term fix we'd like people to have the community test and see if this has fixed the issue across multiple platforms and not the small dev/CB test teams. Attached is a file which will go to your DCS folder under /mods/aircraft/AV8BNA/ Cockpit/MPCD/indicator/TPOD Our team seems to thing that this is where the bug is originating from. What this file will do is DISABLE the MGRS coordinate data and hopefully rectify the issue. IF this does solve the problem please let us know. IF IT DOES NOT. We need either the .trk file or if you get a CTD, then we need the log from your saved games/ dcs folder/ log folder instead. You should also describe IN DETAIL what steps you are doing in order, which gives the fail or CTD. If you can also upload the .miz file you got the fail or CTD on as well there is the possibility it may be due to the ME not liking the GBUs. I know that together we can all work together and get this solved, as we need a larger test base to get things working, we're asking YOU to help us out as sort of a huge OB Test team. I hope this helps guys. TPOD_COMMON_DATA.lua