BeerNfrites

When is it expected to make it into a release?

Are you 100% sure these aren’t neutral dot labels? I run a Quest Pro on godlike through VD, MSAA with quad views but set at 100%. I’m running PD at 1.0. The dots I see are very faint and are visible at 14nm (if I don’t know where to look I have a hard time seeing them) by about 9nm they are replaced by the model, still barely visible. If anything, I find it more difficult to maintain tally under 3-4nm.

Has it ever been communicated by ED what the end goal here is? e.g. we expect a fighter sized aircraft to be spotted at 3/6/9/12nm against a clear sky in daylight. Is there a list of headsets which have had the spotting dots adjusted. As I read that the Quest Pro had been reworked but they still aren't great IMO.

I generally don’t use zoom but allow myself in the A10 as I read that it wouldn’t be uncommon for A10 pilots to use binoculars. The main problem for me with zoom in vr is that even though I have 1000s of hours in flight sims in VR, zooming can still cause me to get sick feeling.

Last update seems good after disabling quad views. With quad views on at x1.1 dots don’t render with it off they render at about 9nm and don’t appear massive. Still seems quite a bit away from parity with monitors as a quick test and what I was seeing at 9nm on vr was visible out to at least 15nm on monitor

fwiw everyone uses openXR now, unless you specifically force steamVR. I'll see how I get on if i turn off quad views.

Are you using Quad Views? I'm running Virtual Desktop godlike, with quad views at 1.1 and DLAA and literally have no dots now at any range.

Yes the upper/left dot is the label and the lower right is the spotting dot. If I switch to abbreviated that is displayed below the aircraft like a blue or red ^ arrow. I'll check what the difference is between left/right and mirror. I think I have my mirror to display left eye. The screen shot was captured from the mirror. The following was captured through the headset screenshot function, you can see the dot is centred on this but still above the model. The spotting dot is not visible due to close range. My config says the same as you have res[last_x] = {"·","CenterCenter",0,opacity,0,2} edit: This was all pre-patch.

Definitely not how they display for me. I have a clearly visible grey label dot above the plane model and then as I zoom out the spotting dot appears below this. I tried to take a screenshot but it doesn't appear as visible or defined on the mirror as in HMD. I haven't ever changed my spotting dots config file and was on open beta previously. Screenshot shows dot neutral label and spotting dot.

FWIW neutral dot labels don’t cover the plane or ground unit, they are positioned as default above (the might flip to below in some instances) the unit they are labelling.

I had issues getting my polling rate to stick in ghub. IIRC the way I solved it was to create a profile and then save that profile to the local memory of the mouse. It was an absolute pain but did eventually manage to get it to stick. I would check, but I vowed to never go near the software again once I got it sorted. I tested using a browser based mouse polling test.

Does this idea of basing everything in reality extend to zoom and being able to swivel your head 180°?

Over 6 months and no one’s even bothered to look at the tracks for this, another abandoned module. BS3 just a cash grab.

Is the download still working for this? I double click to install into streamdeck but nothing shows, just an empty profile.

This is exactly what I'm experiencing. I've been using the P51 free flight instant action on Normandy to test different settings and nothing so far has shown a spotting dot. I load in at roughly 10nm from a pair of P51s in front, I can use labels to see the distance and then cycling through to turn off the labels to check if there are any spotting dots. They never appear. I can 'spot' the planes at roughly 4nm but these are just the single pixels of the models being rendered and not spotting dots. I'm running a Quest Pro @ 1.2 PD, Quad Views at 1.35x for the focus area. Switching between all the different AA modes makes no difference, switching between improved and default spotting dots makes no difference. At the moment for me it's like spotting dots are turned off.

How long is the early access planned to be for this?

Is this list of target sizes still correct? I’ve been trying to hit Ivanov with target size setting set to medium but each missile just flys past the ships. edit: switched to small target setting and hit ivanov cargo ships.

Has it been acknowledged that there is a problem that needs addressing or are we still at the stage of gathering data? I keep seeing statements that not everyone has seen performance drops and feedback has been mixed. I feel personally like the blame is on me, it’s my fault my performance has gone down, rather than there being an issue with the release that needs fixed.

Did you ever get this to work? The ‘pedals without springs and ffb’ still trims you rudder along with your cyclic as far as I can tell.

This has nothing to do with the module

If you have a waypoint for the target then designate it as a TGT and that'll slew your pod to it. Or if you don't have a waypoint you can use the HMD in A/G mode to designate a target and then from there use the pod to fine tune the designation point.

Once you select it you should set it as a/a and then as you move your curser on either the SA, HSI or Radar the BRA from bullseye is shown in the top left (I think, not at the sim at the moment to double check)

I think bullseye is set as WP59 or 58 as standard, I'm sure I've found it already set in at least any mission which has referred to bullseye for BRA calls. Even without F10 map, the kneeboard maps work and you can update your position on them.

Issues on mission 10 part 2. I mentioned it on another topic. Poodle, takes forever to get going, looks like he flys away to wp 0.

Did this mission last night and again tonight. Maybe it was just bad luck but Poodle seemed to have difficulty getting on his way to waypoint 4 tonight after the update, he flew away from it before turning around, also very slowly. He was ok last night pre-update.