fixed F86 radar gunsight solution incorrect

[Squiffy]

Thanks NineLine,

They are very sensitive to negative G too. Every once and a while I'll jam them up just as I line up on a low six surprise, because I overshoot a bit. A tiny bit of pressure on the sitck and bang, no guns for 5 minutes and a mad dive to lower altitude. "Selected" gun heat would help bring them back too but I need to practice that.

[MiG21bisFishbedL]

On 1/6/2022 at 4:13 PM, NineLine said:

 I know you guys get tired of hearing the same thing, but I will do my best to see if its something someone can take some time to do.

You're doing your job, so none of the frustration is on you, bud. Thanks for this.

[EnvyC]

On 4/12/2021 at 2:40 PM, MiG21bisFishbedL said:

It's obscene how long this has taken. If this is the kind of attention gunfighters are due, WEW I have a hard time recommending the WWII side to newbies.

Theres many reasons not to recommend DCS WW2 to anyone (many reasons to do the opposite in fact too), however this isn't one of them. While the WW2 bullet is too slow in comparison to real life counterpart it does harmonise with the K14 far better than the F86s.

https://gfycat.com/quarterlyshamefulirishdraughthorse

https://gfycat.com/impartiallonecirriped

https://gfycat.com/biodegradablerespectfulasianporcupine

gifs courtesy of Shallot, not my content

 

On 1/7/2022 at 9:13 AM, NineLine said:

Yes, overheating is the change I am looking for, its on my list to bump when the team gets back, I know you guys get tired of hearing the same thing, but I will do my best to see if its something someone can take some time to do.

Mate you're doing your best and we're all appreciative of your efforts.

Edited January 24, 2022 by EnvyC

[JokerMan]

The older thread was closed before any confirmation of fix was announced so bumping this one now!

This old thread was started in May 2, 2016.  It's now 2022 and in this new thread started April 9. On Dec 9, 2021 , it's getting another push/kick. 

Frankly, this "still being investigated" status is disappointing at best. The investigation has been done in truth, a resolution testing and verified and yet the official module seemingly cannot be updated. 

S!

 

Joker 

 

Edited February 1, 2022 by JokerMan
spelling

[SoW Reddog]

On 1/6/2022 at 10:13 PM, NineLine said:

Yes, overheating is the change I am looking for, its on my list to bump when the team gets back, I know you guys get tired of hearing the same thing, but I will do my best to see if its something someone can take some time to do.

Nineline,

Can you confirm;

a) that the bullet speed has been accepted as wrong

b) that the barrel warp from overheating has been accepted as wrong

c) that the two things are NOT the same issue, and while linked, either one alone is not the cause of the woes reported for the past 5+ years?

d) That a fix to both a and b is technically possible

e) The time required to do so.

 

Having bought the Sabre a number of times for Squadron mates, I am somewhat aggrieved that it STILL does not work as expected and promised, it simply is not fit for purpose. (Yes, in all other regards the module is wonderful, but if I wanted a cockpit simulator and a flight model only, I'd have bought a civilian flight sim...)

You have, for YEARS strung us along with false promises, it's always "Jam Tomorrow". If you personally cannot get this achieved (and the evidence would suggest you're not important enough to do so), then who can? How do we escalate this? Do I have to track down Nick Grey in person and try to persuade him to honour his commitments?

[NineLine]

The issue is reported, the team has not had time to get back to it yet. Management was noted on the report, but we just haven't had time to get back to it.

I appreciate your frustrations, but saying things like I have made false promises or I am not important enough to get your bug looked at is not fair or helpful, I would assure you that Nick is aware, but again, its just not had development time to get it done. You can try and hunt him down, but I think its not an approach that will help. 

[SoW Reddog]

10 hours ago, NineLine said:

The issue is reported, the team has not had time to get back to it yet. Management was noted on the report, but we just haven't had time to get back to it.

I appreciate your frustrations, but saying things like I have made false promises or I am not important enough to get your bug looked at is not fair or helpful, I would assure you that Nick is aware, but again, its just not had development time to get it done. You can try and hunt him down, but I think its not an approach that will help. 

Thanks Nineline for not answering any of the questions posed. So the official position is that 5 years is not enough time to squash a bug? Good to know. I'll check back in next week and see if that's been long enough. And so on.

[NineLine]

When there is a fix it will be in the change log, you can ask as many times as you like, but it will be done when we have time, I have once again asked for an update, that is all I can do.