Jump to content

Recommended Posts

Posted

If its in front of me then it doesnt belong there. That is like a bug that isnt supposed to be there. 

AWAITING ED NEW DAMAGE MODEL IMPLEMENTATION FOR WW2 BIRDS

 

Fat T is above, thin T is below. Long T is faster, Short T is slower. Open triangle is AWACS, closed triangle is your own sensors. Double dash is friendly, Single dash is enemy. Circle is friendly. Strobe is jammer. Strobe to dash is under 35 km. HDD is 7 times range key. Radar to 160 km, IRST to 10 km. Stay low, but never slow.

Posted
2 minutes ago, WildBillKelsoe said:

If its in front of me then it doesnt belong there. That is like a bug that isnt supposed to be there. 

You keep saying that but what devs can do about it when not even you can replicate it?

🖥️ Win10  i7-10700KF  32GB  RTX4070S   🥽 Quest 3   🕹️ T16000M  VPC CDT-VMAX  TFRP   ✈️ FC3  F-14A/B  F-15E   ⚙️ CA   🚢 SC   🌐 NTTR  PG  Syria

Posted
6 minutes ago, draconus said:

You keep saying that but what devs can do about it when not even you can replicate it?

how about investigate it?

AWAITING ED NEW DAMAGE MODEL IMPLEMENTATION FOR WW2 BIRDS

 

Fat T is above, thin T is below. Long T is faster, Short T is slower. Open triangle is AWACS, closed triangle is your own sensors. Double dash is friendly, Single dash is enemy. Circle is friendly. Strobe is jammer. Strobe to dash is under 35 km. HDD is 7 times range key. Radar to 160 km, IRST to 10 km. Stay low, but never slow.

Posted
8 minutes ago, WildBillKelsoe said:

how about investigate it?

That's simply not how it works in software industry. Investigations cost time and money.

🖥️ Win10  i7-10700KF  32GB  RTX4070S   🥽 Quest 3   🕹️ T16000M  VPC CDT-VMAX  TFRP   ✈️ FC3  F-14A/B  F-15E   ⚙️ CA   🚢 SC   🌐 NTTR  PG  Syria

Posted
6 hours ago, draconus said:

That's simply not how it works in software industry. Investigations cost time and money.

well I am happy you mentioned the money because I paid for a product that is apparently bugged.. 

AWAITING ED NEW DAMAGE MODEL IMPLEMENTATION FOR WW2 BIRDS

 

Fat T is above, thin T is below. Long T is faster, Short T is slower. Open triangle is AWACS, closed triangle is your own sensors. Double dash is friendly, Single dash is enemy. Circle is friendly. Strobe is jammer. Strobe to dash is under 35 km. HDD is 7 times range key. Radar to 160 km, IRST to 10 km. Stay low, but never slow.

Posted
57 minutes ago, WildBillKelsoe said:

well I am happy you mentioned the money because I paid for a product that is apparently bugged.. 

Then prove it.

🖥️ Win10  i7-10700KF  32GB  RTX4070S   🥽 Quest 3   🕹️ T16000M  VPC CDT-VMAX  TFRP   ✈️ FC3  F-14A/B  F-15E   ⚙️ CA   🚢 SC   🌐 NTTR  PG  Syria

Posted
1 hour ago, draconus said:

Then prove it.

there is your proof...

AWAITING ED NEW DAMAGE MODEL IMPLEMENTATION FOR WW2 BIRDS

 

Fat T is above, thin T is below. Long T is faster, Short T is slower. Open triangle is AWACS, closed triangle is your own sensors. Double dash is friendly, Single dash is enemy. Circle is friendly. Strobe is jammer. Strobe to dash is under 35 km. HDD is 7 times range key. Radar to 160 km, IRST to 10 km. Stay low, but never slow.

  • 3 weeks later...
Posted (edited)

 

On 4/23/2023 at 7:47 AM, Flappie said:

Thanks for the video. It helps understanding what's happening. Now, we need a DCS track so devs can reproduce this issue and fix it for good.

 

On 4/27/2023 at 9:21 AM, WildBillKelsoe said:

there is your proof...

  It may be “proof” but what devs need to investigate a bug is a track. The guidelines for reporting bugs require them. And even then often you can do big reports without them. But in scenarios like this where wierd things happen, and Flappie saying you need a track, you’re going to need a track with the issue in order to have ED take a look at it. As Flappie said, it helps them reproduce it, see what caused it, and if new patches have fixed it. You can’t do such with a video 

“well I am happy you mentioned the money because I paid for a product that is apparently bugged.. ”

  You paid for flight simulator, and it delivers on its features.  However this is a minor distracting graphical bug that doesn’t interfere with normal play, seemed to happen once and never again. So don’t expect it to be very high priority. But I can say Flappie is VERY GOOD at Atleast checking your track and following up with ED if you post one. 

Edited by AeriaGloria
  • Like 1

Black Shark Den Squadron Member: We are open to new recruits, click here to check us out or apply to join! https://blacksharkden.com

E3FFFC01-584A-411C-8AFB-B02A23157EB6.jpeg

Posted

To report someone, need be reported propperly

 

For Work/Gaming: 28" Philips 246E Monitor - Ryzen 7 1800X - 32 GB DDR4 - nVidia RTX1080 - SSD 860 EVO 1 TB / 860 QVO 1 TB / 860 QVO 2 TB - Win10 Pro - TM HOTAS Warthog / TPR / MDF

Posted
19 hours ago, AeriaGloria said:

 

 

  It may be “proof” but what devs need to investigate a bug is a track. The guidelines for reporting bugs require them. And even then often you can do big reports without them. But in scenarios like this where wierd things happen, and Flappie saying you need a track, you’re going to need a track with the issue in order to have ED take a look at it. As Flappie said, it helps them reproduce it, see what caused it, and if new patches have fixed it. You can’t do such with a video 

“well I am happy you mentioned the money because I paid for a product that is apparently bugged.. ”

  You paid for flight simulator, and it delivers on its features.  However this is a minor distracting graphical bug that doesn’t interfere with normal play, seemed to happen once and never again. So don’t expect it to be very high priority. But I can say Flappie is VERY GOOD at Atleast checking your track and following up with ED if you post one. 

 

Maybe proof? No I paid the artefacts to show up on the video to start a thread and tarnish the product 🤡 the only way I retain tracks on my drive is to be on the beta testers team. Since I am not, the requirement for a track seems odd. At least to a casual layman dont you think.
 

I think I drove my point home.

AWAITING ED NEW DAMAGE MODEL IMPLEMENTATION FOR WW2 BIRDS

 

Fat T is above, thin T is below. Long T is faster, Short T is slower. Open triangle is AWACS, closed triangle is your own sensors. Double dash is friendly, Single dash is enemy. Circle is friendly. Strobe is jammer. Strobe to dash is under 35 km. HDD is 7 times range key. Radar to 160 km, IRST to 10 km. Stay low, but never slow.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...