Jump to content

Recommended Posts

Posted

That explains why the latest iteration looks fine to me. I haven't touched PD since I moved away from my Rift CV1.

Spoiler

Ryzen 7 9800X3D | 96GB G.Skill Ripjaws M5 Neo DDR5-6000 | Asus ProArt RTX 4080 Super | ASUS ROG Strix X870E-E GAMING | Samsung 990Pro 2TB + 990Pro 4TB NMVe | VR: Varjo Aero
VPC MT-50CM2 grip on VPForce Rhino with Z-curve extension | VPC CM3 throttle | VPC CP2 + 3 | FSSB R3L | VPC Rotor TCS Plus base with SharKa-50 grip | Everything mounted on Monstertech MFC-1 | VPC R1-Falcon pedals with damper | Pro Flight Trainer Puma

OpenXR | PD 1.0 | 100% render resolution | DCS graphics settings
Win11 Pro 24H2 - VBS/HAGS/Game Mode ON

 

Posted

Feedback after latest update on Pimax Crystal and 1.1 PD:

Visibility is back to before the controversial change - I see absolutely no spotting dots whatsoever. I assume they are back to 1 pixel - invisible on Crystal.

Looks like people on other headsets are still unhappy as well - their dots are still too large - so you've made everyone unhappy now.

I was under the impression that the current dots are supposed to depend on the headset - why does it not work for anyone then? Very disappointing.

 

Posted
10 minutes ago, PawlaczGMD said:

I was under the impression that the current dots are supposed to depend on the headset - why does it not work for anyone then? Very disappointing.

ED is working on making it headset dependent, but that is not implemented yet.

  • Like 1
Posted
3 minutes ago, rob10 said:

ED is working on making it headset dependent, but that is not implemented yet.

Well, TBH until that's implemented, ED might just as well revert to before the change that made 90% of people unhappy. Now 100% are unhappy, I will not see any dots on either this or the original resolution scaling.

Looking forward to device dependent dots though, that's a good idea.

  • Like 1
Posted
On 11/4/2024 at 12:57 AM, PawlaczGMD said:

Feedback after latest update on Pimax Crystal and 1.1 PD:

Visibility is back to before the controversial change - I see absolutely no spotting dots whatsoever. I assume they are back to 1 pixel - invisible on Crystal.

Looks like people on other headsets are still unhappy as well - their dots are still too large - so you've made everyone unhappy now.

I was under the impression that the current dots are supposed to depend on the headset - why does it not work for anyone then? Very disappointing.

 

It's ok for the Pimax Crystal ?

🤔

I9 9900k, RTX3090, 32Go, Nvme SDD, X56, pro rudder pedals, Quest2

  • ED Team
Posted
On 11/3/2024 at 11:57 PM, PawlaczGMD said:

Feedback after latest update on Pimax Crystal and 1.1 PD:

Visibility is back to before the controversial change - I see absolutely no spotting dots whatsoever. I assume they are back to 1 pixel - invisible on Crystal.

Looks like people on other headsets are still unhappy as well - their dots are still too large - so you've made everyone unhappy now.

I was under the impression that the current dots are supposed to depend on the headset - why does it not work for anyone then? Very disappointing.

 

I use PD 1.0 in DCS with the PIMAX Crystal and its perfect for me. 

It is going to be very difficult to make everyone happy no matter what we do, there are way to many variables at play. 

  • Like 1
  • Thanks 1

smallCATPILOT.PNG.04bbece1b27ff1b2c193b174ec410fc0.PNG

Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status

Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal

Posted

It is not their job to make everyone happy. They should make it look real. Quest 3 first because it is the most popular, and then next headsets.

Wysłane z mojego VOG-L29 przy użyciu Tapatalka

  • Like 2

PC: i7 13700k, 64GB RAM 3600MHz DDR4, SSD M.2 Drives, RTX 4090, VR: Quest 3.

VPC MongoosT-50CM2 Grip, VPC MongoosT-50CM3 Throttle, crosswinds rudder pedals, VPC panel CP3, WinWing PTO2

 

Posted (edited)

Are the dots simply based upon the native resolution of the headsets or do they account for pixel density settings? If they try to use the pixel density setting it seems there would be no way to account for all the possible variations.

Edited by SharpeXB
  • Like 1

i9-14900KS | ASUS ROG MAXIMUS Z790 HERO | 64GB DDR5 5600MHz | iCUE H150i Liquid CPU Cooler | ASUS TUF GeForce RTX 4090 OC | Windows 11 Home | 2TB Samsung 980 PRO NVMe | Corsair RM1000x | LG 48GQ900-B 4K OLED Monitor | CH Fighterstick | Ch Pro Throttle | CH Pro Pedals | TrackIR 5

Posted
57 minutes ago, BIGNEWY said:

It is going to be very difficult to make everyone happy no matter what we do, there are way to many variables at play. 

You can at least make half of them happy by providing the option for disabling the dots.

  • Like 4

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

Posted
5 minutes ago, draconus said:

You can at least make half of them happy by providing the option for disabling the dots.

Yes that is the simple Solution let users turn them off .

 If users are happy with the way they look then use them.

why is it so hard to impliment this simple request ?

Just let them play the sim how they want to play the sim.

If devs insist on finding the holy grail then let them do it in private .

Its like DCS is dying before my eyes with all this rubbish going on month after month !

waterman

  • Like 2
  • Thanks 1
Posted
2 hours ago, waterman said:

Yes that is the simple Solution let users turn them off .

 If users are happy with the way they look then use them.

why is it so hard to impliment this simple request ?

Because the consequences aren't very desirable. Will you accept the pop-in? The scintillation as a target hovers at the edge of visibility? The complete uncertainty as to how visible you are to others relative to how well you can see them?

❧ ❧ Inside you are two wolves. One cannot land; the other shoots friendlies. You are a Goon. ❧ ❧

Posted

The simple Solution let users turn them off .

If users are happy with the way they look then use them.

Many users have spent a lot of money on vr setups.

Many users just want to enjoy what they have purchased and fly around without getting too serious about it.

They should decide whats best for themselves and what they want turned on or off.

Not the few DCS rivet counters deciding for them.

 

 

  • Like 1
Posted
5 hours ago, BIGNEWY said:

I use PD 1.0 in DCS with the PIMAX Crystal and its perfect for me. 

It is going to be very difficult to make everyone happy no matter what we do, there are way to many variables at play. 

In what sense is it perfect for you? I don't see the difference from before you've increased the dots because people were complaining about visibility. Do you see a difference from then? At what distance can you see a dot for a fighter?

Genuine question, I just don't see any dots right now. Before the latest update, I thought they were a little too big, but now it's gone for me.

Posted

The insane part is they want to make them headset dependent but refuse to allow VR users to turn them OFF.

I fundamentally do not understand why OFF is not an option!?!?

  • Like 3
Posted
15 hours ago, BIGNEWY said:

It is going to be very difficult to make everyone happy no matter what we do, there are way to many variables at play. 

True, as others said, is going to be easy to add a gameplay option to turn it on and off. Like labels right now.

  • Like 2
Posted
12 minutes ago, Parkour said:

The insane part is they want to make them headset dependent but refuse to allow VR users to turn them OFF.

I fundamentally do not understand why OFF is not an option!?!?

Could it be they are dependant on the feedback of those VR users?

Modules: A-10CII | F-5E | AV-8B | M-2000C | SA342| Ka-50-III | Fw 190D-9 | Mi-24P | SU-33 | F-4E | F-14B | C-101CC | F-86F | AH-64D | F-16C | UH-1H | A-4E-C | AJS-37 | P-47D | P-51D | Bf 109K-4 | CA | SC
Maps: Cold War Germany | Nevada | Syria | Persian Gulf | South Atlantic | Kola | Sinai | Normandy | Channel
Setup: Ryzen9 5950X | 64GB DDR4 | RTX 4090 | 2TB M.2 NVMe | TM Warthog & TFRP Rudder | Reverb G2 | OpenXR/TK | Win10
Affiliation: [TM]Tigermercs

Posted
55 minutes ago, nachomaga said:

True, as others said, is going to be easy to add a gameplay option to turn it on and off. Like labels right now.

And again, since they are part of the simulation and not a UI element, they can't be treated the same as labels. That's ultimately why it shouldn't be an option even for pancake users.

Now, granted, there are some sim options that can be toggled, like wake turbulence and g-effects, but the difference there is that when you force them one way or the other, the effect is universal and not dependent on the client's settings — after all, that's the whole point of forcing them: so the client has no say. The spotting dots are so dependent on the graphics and display settings, and display type on top of that, that no such universality can be assured. Quite the opposite.

The reason we are getting these new dots is because of that very issue, where there is no telling how it will turn out if you just let the geometry do its thing. The spotting dots are exhibiting similar issues, but unlike the raw geometry option, it's actually fixable.

And…

1 hour ago, Parkour said:

I fundamentally do not understand why OFF is not an option!?!?

…that also explains why. Because it's just an interim thing that should ultimately go away for everyone. VR is in a sense just ahead of the curve.

❧ ❧ Inside you are two wolves. One cannot land; the other shoots friendlies. You are a Goon. ❧ ❧

Posted (edited)
18 hours ago, draconus said:

You can at least make half of them happy by providing the option for disabling the dots.

There is a bug causing dots to dissappear.

You can manually trigger the bug atm if that's what you'd prefer. Instructions linked.

And for those suffering from the dots disappearing in busy missions, the fix should help a good bit.

Edited by MoleUK
  • Thanks 1
Posted
20 hours ago, BIGNEWY said:

I use PD 1.0 in DCS with the PIMAX Crystal and its perfect for me. 

It is going to be very difficult to make everyone happy no matter what we do, there are way to many variables at play. 

I hope you will achieve the same quality with the other headsets
  • Like 1

I9 9900k, RTX3090, 32Go, Nvme SDD, X56, pro rudder pedals, Quest2

Posted
14 hours ago, MoleUK said:

There is a bug causing dots to dissappear.

You can manually trigger the bug atm if that's what you'd prefer. Instructions linked.

Joke or just trolling?

  • Like 1

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

Posted (edited)
2 hours ago, draconus said:

Joke or just trolling?

Neither.

I have been flying with invisible dots for months, and I have hated it. It puts me off playing entirely.

But I understand users like yourself feel the complete opposite and hate the presence of the dots themselves, so i'm offering you a solution.

It's up to you whether you use it or not.

Edited by MoleUK
Posted
2 minutes ago, MoleUK said:

so i'm offering you a solution

It's trolling then.

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

Posted (edited)
14 minutes ago, draconus said:

It's trolling then.

Believe it or not, I can't fundamentally change the way the entire spotting system works from my end. I can only tweak things.

As I said, if you don't want to use the current workaround that's fine. It's far from ideal, both as a way to get dots to re-appear or disappear. But it's there.

Edited by MoleUK
  • Like 1
Posted
When Bignewy says ''It is going to be very difficult to make everyone happy no matter what we do'' 
I still wonder which VR headsets will benefit from the new system and which will have nothing.
If in the future I am wrong I will apologize
 
  • Like 1

I9 9900k, RTX3090, 32Go, Nvme SDD, X56, pro rudder pedals, Quest2

Posted (edited)

I have the Quest 3 and my Pixel Density is 1.3
With 1.3 I see the Black Squares very sharp and large. 
With a Pixel Density of 1.0 they look a bit blurrier and smaller. If I set the Pixel Density to 1.1 they look larger and sharper again. 

Unfortunately still no solution from ED?  😕

 

 

Edited by Robi Hobby
Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

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