RAZBAM_ELMO

Well firstly misquoting me as saying get lost our SME said so is wrong and incorrect so let's squash that bug off the bat. Secondly if you don't want to hear what I'm passing along from the team and from actual people who fly these things nearly everyday thats fine. Ignore me but do not try to detract FACT from what YOU personally want out of the game. We do this not only for the consumer market but for ACTUAL MILITARY PILOTS doing ACTUAL MILITARY TRAINING. It goes hand in hand, so while I appreciate criticism and every bug reported, when the resulting resolution is questioned its kind of silly. We spent all that time working and correcting a fault which was made and then it turns out its right but people don't like it one way. Now the idea of adding the threat codes in is a possibility and has been suggested, when and if it may appear depends on whats left to work on in the A/C and what else is on the plate. What were really hoping for is ED to add DTC capabilities to all modules in the future to correct these. Sent from my SM-N960F using Tapatalk

Weird. Its like we thought of exactly that and are testing it internally..... weird I tell ya.

Why need to customize it if we've received and updated the RWR based on AdA and active SME input? If you want to modify things outside of the base offering thats fine but if weve got it to the point where it as as realistic as it can be why do we need to add things that were not suggested by our SMEs and the AdA in the first place? Like i said above if and when A DTC becomes available to 3PDs then perhaps but were modelling a certain aircraft from a certain period of time with certain features on it.

Alot of this has to deal with having no DTC capability with the current DCS engine but hopefully in the future we can get something like this to happen and allow for more internal customization via ME or Special Tabs to make features more personal to the pilot or mission specific.

YEp. We will work with what we have and then look at adding new systems.

While correct we cannot change that the locks dont happen because of contrast in DCS. The game doesnt work that way. For CCD or TV it simply asks if there is a unit where the sensor is looking and the game will say yes or no. For IR it has to point at the center of the 3D structure model to lock. So while unrealistically perfect that is as much as we can manage with how the game interprets sensors and locking logic

please upload the trk file here not on a secondary link.

Glad to see that the conversation is staying civil and constructive everyone, keep it up.

Interesting. Do you have a tutorial video on how to install it and get it working?

Hi Rudel, is this issue still present in 2.5.6.55743 for you?

Hi Gozr, are you still experiencing this issue in the latest update 2.5.6.55743? If so could you please provide a .trk file so we can see what happening and resolve the issue, thanks.

Ok so a few things to touch on there. !. By what do you mean "it seems"? I encourage discussion and constructive criticism, however that dialogue must contain the evidence for a statement. Only saying it is so because it "seems" that way is no way in furthering the discussion. Please provide evidence to your statement prior to making a claim. 2. Again I would like to look into this but it requires evidence. Actually had a very very VERV large conversation with our SME into expanded functions of some systems to be announced at a later date. 3. Yes they are not implemented at this time. We could throw in something reminiscent of the LABS system in the F-86 sabre but that would not be realistic to the harrier. We are however exploring options to see how it can best be implemented with what is offered. While it may seem easy enough on the outside like " oh just teach it ballistic traj. data from a Mk.82" Well we thought it would be that easy too however the complex systems in the harrier has made implementing a reliable version very difficult. We are however constantly using CB testers and various versions of a base system to see what can work and what wont.

As many of you are aware, I am going throuh ALL of the bug reports to make sure any outstanding issues are dealt with. So In order to help me with older bugs and newer ones that come up I ask that you provide the following when creating a bug post. 1.Start with making sure it is the latest OB release version. 2.Make sure you have a clean install, meaning, no mods or other scripts. 3. A detailed description of how you are encountering the bug ( and I mean detailed) 4. If you get a crash I need a .log file because .trk files aren't recorded in the case of a CTD ---- OR --- if you don't get a crash I need a .trk file to pass along to the team. 5. IF POSSIBLE, pictures, screenshots or even a video showing what's happening. Make sure that you're report is as clear and concise as possible to help us find exactly what's going wrong. Make sure you are following the 1.16 Rule guidelines outlined by ED regarding declassified documents. If you want to help a fellow flyer with the issue if you are having the same problem or know what they may be doing wrong before we help them, make sure you are doing so in a friendly, patient and constructive manner. I will not tolerate belligerence or mocking of any kind. This is a place to learn, not to insult or put people down due to lack of knowledge on the subject matter. Helping someone properly then may actually help you or others in-game down the road. We get out what we put in ladies and gents. Be the example others want to follow.

As many of you are aware, I am going throuh ALL of the bug reports to make sure any outstanding issues are dealt with. So In order to help me with older bugs and newer ones that come up I ask that you provide the following when creating a bug post. 1.Start with making sure it is the latest OB release version. 2.Make sure you have a clean install, meaning, no mods or other scripts. 3. A detailed description of how you are encountering the bug ( and I mean detailed) 4. If you get a crash I need a .log file because .trk files aren't recorded in the case of a CTD ---- OR --- if you don't get a crash I need a .trk file to pass along to the team. 5. IF POSSIBLE, pictures, screenshots or even a video showing what's happening. Make sure that you're report is as clear and concise as possible to help us find exactly what's going wrong. Make sure you are following the 1.16 Rule guidelines outlined by ED regarding declassified documents. If you want to help a fellow flyer with the issue if you are having the same problem or know what they may be doing wrong before we help them, make sure you are doing so in a friendly, patient and constructive manner. I will not tolerate belligerence or mocking of any kind. This is a place to learn, not to insult or put people down due to lack of knowledge on the subject matter. Helping someone properly then may actually help you or others in-game down the road. We get out what we put in ladies and gents. Be the example others want to follow.

As many of you are aware, I am going throuh ALL of the bug reports to make sure any outstanding issues are dealt with. So In order to help me with older bugs and newer ones that come up I ask that you provide the following when creating a bug post. 1.Start with making sure it is the latest OB release version. 2.Make sure you have a clean install, meaning, no mods or other scripts. 3. A detailed description of how you are encountering the bug ( and I mean detailed) 4. If you get a crash I need a .log file because .trk files aren't recorded in the case of a CTD ---- OR --- if you don't get a crash I need a .trk file to pass along to the team. 5. IF POSSIBLE, pictures, screenshots or even a video showing what's happening. Make sure that you're report is as clear and concise as possible to help us find exactly what's going wrong. Make sure you are following the 1.16 Rule guidelines outlined by ED regarding declassified documents. If you want to help a fellow flyer with the issue if you are having the same problem or know what they may be doing wrong before we help them, make sure you are doing so in a friendly, patient and constructive manner. I will not tolerate belligerence or mocking of any kind. This is a place to learn, not to insult or put people down due to lack of knowledge on the subject matter. Helping someone properly then may actually help you or others in-game down the road. We get out what we put in ladies and gents. Be the example others want to follow.

As many of you are aware, I am going throuh ALL of the bug reports to make sure any outstanding issues are dealt with. So In order to help me with older bugs and newer ones that come up I ask that you provide the following when creating a bug post. 1.Start with making sure it is the latest OB release version. 2.Make sure you have a clean install, meaning, no mods or other scripts. 3. A detailed description of how you are encountering the bug ( and I mean detailed) 4. If you get a crash I need a .log file because .trk files aren't recorded in the case of a CTD ---- OR --- if you don't get a crash I need a .trk file to pass along to the team. 5. IF POSSIBLE, pictures, screenshots or even a video showing what's happening. Make sure that you're report is as clear and concise as possible to help us find exactly what's going wrong. Make sure you are following the 1.16 Rule guidelines outlined by ED regarding declassified documents. If you want to help a fellow flyer with the issue if you are having the same problem or know what they may be doing wrong before we help them, make sure you are doing so in a friendly, patient and constructive manner. I will not tolerate belligerence or mocking of any kind. This is a place to learn, not to insult or put people down due to lack of knowledge on the subject matter. Helping someone properly then may actually help you or others in-game down the road. We get out what we put in ladies and gents. Be the example others want to follow.

As many of you are aware, I am going throuh ALL of the bug reports to make sure any outstanding issues are dealt with. So In order to help me with older bugs and newer ones that come up I ask that you provide the following when creating a bug post. 1.Start with making sure it is the latest OB release version. 2.Make sure you have a clean install, meaning, no mods or other scripts. 3. A detailed description of how you are encountering the bug ( and I mean detailed) 4. If you get a crash I need a .log file because .trk files aren't recorded in the case of a CTD ---- OR --- if you don't get a crash I need a .trk file to pass along to the team. 5. IF POSSIBLE, pictures, screenshots or even a video showing what's happening. Make sure that you're report is as clear and concise as possible to help us find exactly what's going wrong. Make sure you are following the 1.16 Rule guidelines outlined by ED regarding declassified documents. If you want to help a fellow flyer with the issue if you are having the same problem or know what they may be doing wrong before we help them, make sure you are doing so in a friendly, patient and constructive manner. I will not tolerate belligerence or mocking of any kind. This is a place to learn, not to insult or put people down due to lack of knowledge on the subject matter. Helping someone properly then may actually help you or others in-game down the road. We get out what we put in ladies and gents. Be the example others want to follow.

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

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

I agree it can be confusing at times. Perhaps in the future we can all work together with other 3PDs and ED to come up with a common definitive system to better describe a modules state. Thats what creative and constructive feedback will lead to when we all work together. Sent from my SM-N960F using Tapatalk

In Ecuador my friend. However the team is made up from various nationalities. I myself am from Canada.

Gentlemen moving forward if we continue to be negative towards each other, we will not progress. I encourage criticism and discussion. However, when we start hurling insults and begin talking each other down, it serves no purpose but puts us back where we started. Lets constructively work together to better our relationship.

Very cool, looking at this with interest