reported Qeshm Island airport issue, Floating whitelines

[skywalker22]

There is a the right white line along the runway 23 in the air, floating. Its really hard to tell from the pictures only, you should really see it in person. But it looks like white lines are way off the ground, floating.

Edited October 2, 2024 by skywalker22

[Flappie]

Thanks for the heads up.

Issue reported.

[Grodin]

Sligthtly hard to tell from a screenshot, but the north side runway side marker is floating in the air. From some angles you can see "under it", but from that angle the marking will disappear completely.

[boerdi]

Runway marker line doing extradimensional stuff

Open Beta 2.8.8.43704

 

[BIGNEWY]

reported

thanks

[BIGNEWY]

threads merged

[Flappie]

A fix is on its way.

[average_pilot]

Since it's taking a while, is there any temporal workaround or manual fix?

[Flappie]

I don't think so.

[Tom P]

This was reported in 2022 and is still a thing. What's the hold up, It's not like there is that much on PG or at Qeshm's airfield. It's not a game breaker or anything but still it's been 489 days since first reported, and 170 days since a fix is on the way. 

[BIGNEWY]

At the moment its all about our terrain teams having free time, they are currently busy with the Free Marianas WWII terrain, Iraq and Afghanistan. 

I will bump the reports internally but I can not say when for a fix. 

thanks

[joey45]

At a guess they'll probably fix some other stuff as well  and bundle it in one 30 gig update.

[Tom P]

639 days = 21 months / 1.75 years

[Flappie]

I've just bumped the report.

[Tom P]

720 days / 23 months / 1.97 years and still not fixed.  Afghanistan is released, and Iraq was recently released for pre-purchase.nullnull

[theRealTrickFlare]

Bro, 
They got new super tech coming with Iraq that's going to fix everything ok.
Chill.

[Dangerzone]

51 minutes ago, Tom P said:

720 days / 23 months / 1.97 years and still not fixed.  Afghanistan is released, and Iraq was recently released for pre-purchase.nullnull

Dude. Come on. It hasn't even been 2 years yet. Haven't you heard... ... 2 years^tm is the new 2 weeks^tm. 

[Terry Dactil]

Can someone show me what the problem is here?

If the white line is above ground level I would expect it to cut  through the wheel and  also to disrupt the  line of a shadow edge passing over it

Example of disrupted shadow edge.

 

Edited October 22, 2024 by Terry Dactil

[Dangerzone]

32 minutes ago, Terry Dactil said:

Can someone show me what the problem is here?

If the white line is above ground level I would expect it to cut  through the wheel and  also to disrupt the  line of a shadow edge passing over it

Example of disrupted shadow edge.

 

 

You would be correct, except that in DCS, shadows (especially 'flat shadows') can work differently to save some processing compared to RL - and the shadow itself can sometimes float. (Different issue - not related to this topic - except that it's causing the screenshots not to show correctly). Even when I know very well what the problem is - to me - the shadow appears on the ground in the screenshot - but I know it's definitely not. The problem can't really be seen in the pictures. It's best to take a look at the video for a better explanation (4th post) for what's actually happening. It's even significantly more obvious in VR.

Edited October 22, 2024 by Dangerzone

[Terry Dactil]

48 minutes ago, Dangerzone said:

You would be correct, except that in DCS, shadows (especially 'flat shadows') can work differently to save some processing compared to RL - and the shadow itself can sometimes float. (Different issue - not related to this topic - except that it's causing the screenshots not to show correctly). Even when I know very well what the problem is - to me - the shadow appears on the ground in the screenshot - but I know it's definitely not. The problem can't really be seen in the pictures. It's best to take a look at the video for a better explanation (4th post) for what's actually happening. It's even significantly more obvious in VR.

Thanks.

It all makes sense now, particularly after a closer look at the video.

My mistake assuming 'floating' meant some distance above the surface. 

Probably more accurate to say the white line  is slides on the ground surface.

 

[Dangerzone]

38 minutes ago, Terry Dactil said:

Thanks.

It all makes sense now, particularly after a closer look at the video.

My mistake assuming 'floating' meant some distance above the surface. 

Probably more accurate to say the white line  is slides on the ground surface.

 

I can see why you would say that, but actually - it is floating, not sliding. (in 2-D it may give the appearance of sliding, but in VR - it is definitely floating. You can definitely see it closer to you, and above the ground). You can actually see the ground on the other side of the white line under the line if you get out of the plane and view externally. 

It's as though it has 2 anchor points - one at the west end, and the other 3/4 of the way to the eastern end - and the line is straight - and does not curve with the ground. As such, it is suspended/floating in the air between these too points. 

The video would have shown it much better if he was out of the cockpit, but either way - nothing compares to seeing it in 3D for just how 'in your face' (excuse the pun) it is.

[skywalker22]

3 hours ago, Dangerzone said:

I can see why you would say that, but actually - it is floating, not sliding. (in 2-D it may give the appearance of sliding, but in VR - it is definitely floating.

Also you can notice that by looking into a "2d" picture of a monitor. In VR is just more pronounced.

is it that long ago? A week away of being 2 years now.

[Dangerzone]

On 10/23/2024 at 3:11 PM, skywalker22 said:

Also you can notice that by looking into a "2d" picture of a monitor. In VR is just more pronounced.

is it that long ago? A week away of being 2 years now.

You can notice it in 2D - but you have to be moving to get the effect. (Still shots)

And yes... we're approaching the 2 year mark now.

The thing that ticks me off with this stuff is I'm fairly sure that it was fine when the map was first released - the bug only got introduced 2 years ago. 

It's one thing to say we're working/focused on other projects at the moment to refer to slowing down development maybe of some EA modules... but it's another thing to say we're no interested in fixing something that we've broken that used to be OK because we're focused elsewhere... for 2 years. 

While this isn't a game breaking issue like some other things - it's unfortunately sent a message that it's no priority for them to fix something if they break it after it's been developed. Actions (or lack thereof) speak louder than words.

[Tom P]

Something something passion and support.

[Tom P]

nullHappy 2 year anniversary!!!null