RAZBAM_ELMO

Thanks man, well investigate and get back to you guys.

So the new symbology is not there or you just cant edit the rwr data?

Going to need a .trk file imbedded in the forum cause i cannot access the link you provided

Yup, can't do anything about this, its a DCS wide thing

Hi YoYo. Is this performance issue still present for you in 2.5.6.55743? As most of the team does not possess VR it is difficult for us to test this issue, we usually have to send it to ED's CB testers before we can hear back. Let me know so we can tackle this one thanks.

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

Just checking guys, has this issue been rectified for you all in 2.5.6.55743?

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.

Seen.

Hi guys, does this happen with just the -19P or does it occur with other modules?

Hey man, yup that one and this one have been added to the internal tracker. 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.

Verified with SME, working as intended.

Confirmed values are as intended. SME confirms.

Can we confirm this is still occurring as of the latest OB patch?

Seems this is a user error. Working for internal CB testers on OB release as well as myself. Putting this down as user error.

Seen. Passed along internally.

Known DCS bug, fixed internally for next patch.

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.

trk file please

HOW TO REPORT A BUG 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.