jimiC

Great news thanks

ok well there is a new updater but unfortunately (not the updaters fault) it didnt help, in fact my situation is now worse. can't use either 2.9 ST or MT without cross eye so something has unstuck the settings even further. I now need this tool back ASAP to even play 2.9 at all. (and i won't be bothering to roll back to 2.8 so will just not play until fixed)

good point. yes. i launch 2.9 ST with the updater tool by skatezilla but AFAIK i cant launch MT using the tool so haven't been doing so. (he was working on a new updater though so i will no go search and see if there is an update.) but even then , i was launching MT in 2.8 without the tool and had no issues with the cross eye problem.. so there's still something different going on

not quite. the lua settings (changed or otherwise) do not apply if loaded from the MT bin

as already alluded to in this thread the MT version of 2.9 has undone the VR alignment that was previously resolved with a tool like this. There is currently no way to fix the view in VR for my headset in multithreaded version rendering it un-useable.

yes it seems to work for me in single thread provided i delete the profile it originally created but of course all the good visual improvement settings stuff for 2.9 is in MT

Thanks for the advice but not sure relevant. My alignment is fine in all other applications and in 2.9 ST (including using this tool in 2.9 ST ) However loading in MT doesn't apply the alignment or allow the tool to be used for the MT version

i hope they can address this as a matter of priority given new graphics are tied to the MT version

2.9 has just made my Vive Pro headset revert to a cross eye effect which i corrected years ago (when the tool came out probably?) and now it has forgotten the setting. VR now unuseable in 2.9 edit: will correct myself slightly. MT 2.9. Looks like my settings work in Single thread still but the MT has forgotten it, which is pretty odd considering MT was fine in 2.8 Why on earth would the setting no apply in both, and why would it suddenly stop in 2.9...

+1 .came back to find DICE and VIACOM are busted in MP. genuinely unimpressed with how this has been rolled out. these mods and many others have filled a gap in capability that the core sim should actually cover, adding significant improvement to the user experience, simply incredible they are just being pushed to the side in the name of 'anti cheat' with broad brush strokes. throw that on top of the progressively worse /stagnant core feature and performance of the sim, especially in VR, and its becoming a bit of a pain. make an effort ED.

nope not related. recenter is relative to the cockpit not the helmet and balaclava also note the ihads projection is overlapping with the bezel of the ihads itself i think the head position rel ihads/helmet needs to move a couple cm forwrd Matt's image does a better job of explaining the problem than my OP

hmmm i will give this a go and see if it makes a difference. thanks. yes you're right the screenshot probably wasnt a good illustration of problem but you managed to grasp what i was saying

Please read the OP correctly Num 5/reset VR isnt the issue in this instance. dont think 'head position in cockpit' think 'head position in helmet'. Look at the dodgey textures stuck in front of the lower quarter of the view (its the fire balaclava) and the overhanging helmet at the top. This all serves to reduce the overall FOV in a VR headset already restricted in FOV anyway, not to mention the inside of a balaclava low res texture is ugly to look at.

VR headset type Vive Pro 2. default position on first startup. *note not talking about head position in cockpit , that is adjustable as usual. talking about view position within the body/helmet below image is from left eye. same issue right eye with view of inside of helmet and balaclava

agree with the sentiment in this thread. VR clouds are suboptimal. i woudl go as far as to say there's no different maybe even worse than 2.5 in quality. bland amorphous blobs

they're amorphous and lacking definition in VR. i dont see them as any better than the old clouds currently

i've managed a workaround but it requires (forces) me to use the desktop resolution to render the game on the monitor at the same resolution which previously i didnt do to try and save any spare FPS i could. I still believe the normal settings re full screen and mouse inside window (not vr tab) are not working as they were previously. now onto the visuals... FPS is about the same but its more stable for me. less flucuation. The clouds are... meh.... blurry and amorphous. not sure if its a setting im missin somewhere , i have it set to ultra and i have PD 1x with my steamvr supersampling at 150% in a vive pro.

on investigation i think this may be related to the VR settings for scren resolution and eye rendering on the screen. the 2 sets of settings arent playing nice together. I was able to mitigate the mouse cursor inside game window issue by setting my desktop to match the game res (or vice versa) . previously i have set my game res to be lower than desktop because im not actually using the monitor while in vr. suboptimal solution imo.

Setting the mouse to remain within game window has no effect any more. When using mouse in vr and head tracking to point/click a clickable cockpit item, if it is outside the game window the window loses focus. worked in 2.5x no longer working in 2.7 workaround would be to enter full screen mode. but checking this box has no effect on game window mode using alt-enter results in fullscreen but 2FPS and eventually a crash of vr

haven't been able to effectively fly in 2.7 in VR because the option for mouse to remain within game window no longer works and alt-enter to full screen results in 2FPS

4 attempts over a 12 hour period

no ideas?

inbound salute request rearming see you at ten etc etc . there is literally no second part of the command to give. when i say all commands i mean all. it won't accept any single sentence command i've already attempted a reset of the lua script and re-imported the profile Log below ------------------------------------------ DCS mission | Caucasus FA-18C Case I Carrier Landing Resetting selected units. Player New callsign entered module FA-18C Hornet, unit callsign 111 Nearest ATC: Ticonderoga class. Scanning for new theater. Loading keywords database... TX2 | COMM2: ARC-210 AM 305.000 MHz: no tuned units. TX1 | COMM1: ARC-210 AM 305.000 MHz: no tuned units. Captured sentence: inbound (awaiting additional input) Captured sentence: select (awaiting additional input) Captured sentence: see you at ten (awaiting additional input) Captured sentence: request rearming (awaiting additional input)

Hi all, Went from one day fully working to the next all inputs saying 'awaiting additional input' On load it appears a lot of settings were lost for no particular reason, having re-entered all settings in the config still no joy. any ideas?

edit: I appear to have fixed the above by elevated priv for python I'm curios on the time settings? Is there a setting to adjust from Zulu to local as the missions are being set to Zulu but the theatre is +2