twobells

I'm also having great trouble keeping the F15 straight on take-off which is unusual as I have absolutely no problems with my pedals on any other module. I've set the Saitek axis settings the same as Speedbirds, however, I still have serious problems.

The Rift is the most important flight-sim peripheral development since the TrackIR and leaves that in the shade, the level of immersion is incredible.

I have a feeling the August 2016 update borked many rifts with the dreaded 'hdmi disconnected' error. Subsequently, I am looking to find a way to roll back to 1.6, however, I cannot find the 1.6 firmware.

Note. sale approved by admin. SOLD SOLD

I know this question is directed at Vive owners, however, for the record, you can clearly see every marking, serial number and yes the script around the gauges and switches on the OR. When my OR arrived I had a GTX 970 which worked amazingly well.

Did it affect your DCS framerate at all? TIA

What I did for: Panoramic Encompassing View: I Mapped 'reset view' to my HOTAS then lent forward towards the desk/monitor and hit 'reset.' This gave me a fantastic wide angle point of view, allowing me to easily access any panel. Further, I mapped 'Zoom in slowly' to the left throttle button which instantly zoomed in on any button/screen/switch. Detailed HUD/Sensor View: Again, using the mapped 'reset view' button on my Hotas I sat back firmly in my chair which produced a close-in detailed view of the MFD's and HUD. Wish List: I think it would be brilliant if we could save 'VR view positions' (at least two maybe?). When flying we could instantly change our viewpoint from Detailed Sensor View (DSV) to Panoramic Encompassing View. (PEV) dependent on mission. Admittedly, we can just do that 'on the fly' but no-one wants to fiddle about like that on mission.

Superb stuff! Thanks so much.

Resolved for anyone who has motherboards with a Asmedia USB controller. Solution: Disable Asmedia controller which has proven to be the #1 fault for hdmi disconnects and 'black screen'. __________________

Hey Greg, Could you please post a photo of your rig so we might have a better understanding of your requirements?

I watched that video with great interest, superb flying.

Very informative thanks.

Remember you have the option to turn down cockpit judder in the SA342 'special' option menu. However, I recommend following the brief notes posted in 'multicrew so far' thread, as in: Pilot comes to a hover, sets auto-collective then passes control to his WSO (weapons commander), the WSO has his HOTS set to 'lock' he then changes to manual slews to target then hits slave to target,the SA342 adjusts its heading in line with the Viviane reticle, you should then get a green light from the weapons board and release weapon. gl

I have a DP connector let me try that. resolved Solution: Disabled Asmedia controller which has proven to be the #1 fault for hdmi disconnects and 'black screen'.

Don't forget to hit A to swap controls between the pilot and his gunner/co-pilot.

Isn't it?, incredible.

No, but the controls have been modified. In options select 'general' then click 'ok' then go back to the SA342 control options and your controls should all now be back as you mapped them, hit okay and exit.

Client in testing: 1.5 OB Just a quick run down of my experience so far. Myself and fellow 333VFG member Specter successfully tracked, targeted, released and destroyed 3 sams, however, currently there is no ground stabilization, lasing or fine control as referred to in the updated manual. Once I entered hover then auto collective, my gunner was able to take over horizontal control, slewing to target. When a co-pilot joins your server and selects the co-pilot/gunner position in 'role' below you an invite will appear on the hosts screen, host highlight his name and then select 'accept'. The commander (co/pilot) joins the SA342 and if you hit 'copilot point of view [RCtrl+RShift+Numpad key] ' the commanders (WSO) point of view now encompasses a much wider field of view. To swap controls between the pilot and his commander hit the 'A' key. Piece of advice, tell your gunner to employ his stick for targeting, not the micro-mouse (for slewing) such as the one on the TM Warthog throttle as the control via the joystick is far superior and more importantly pitched correctly. I'd be very interested in feedback from anyone who was able to obtain fine targeting control with the micro mouse. Update: as gunner the user sees a warning panel lit up like a Christmas tree as well as a perm lit caution light. As previously mentioned the micro mouse has very sloppy slew control, however, in this case stick is king. On a second note, the pilot and the gunner need to closely work together, in that the auto hover and auto collective is controlled by the pilot not the gunner (unless as previously mentioned you tap the 'A' key wherein you swap controls) Remember also, that the pilot needs to use the auto slave toggle to roughly position the helicopter for the gunner until you hand off control to him. Check the updated manual for the specifics.

Started having some real trouble only 3 weeks after my Rift arriving, essentially it started with 'hdmi disconnects' throwing me out of DCS but now I get a black screen AND an hdmi disconnect (probably the same thing) but this is whats weird, only in DCS, everything else works fine. So I tried repairing DCS but that didn't work so I assume my next step is a complete re-install... May I ask, has anyone else experienced this issue and have they found a solution? Thanks in advance edit. okay, I have found another thread related to this issue, seems that many Rift owners are suffering these problems, what I don't understand is how my Rift which is only 3 weeks old, worked perfectly all that time in DCS with no problems suddenly have serious issues. http://forums.eagle.ru/showthread.php?t=168053&highlight=disconnecting resolved Solution: Disabled Asmedia controller which has proven to be the #1 fault for hdmi disconnects and 'black screen'.

At what pixel density? I had a factory 'clocked Gainward GTX970 and got at least a 50% increase at 1.8 PD. The game was playable on the 970 but the framerate was pretty low, averaging around 21fps.

Can you please post a screenshot of the 'corrupt square'? I think your issue is related to the 'dreaded yellow splodge' rather than the one shown in my OP. thanks.

Great OP, thanks so much, however, in reference to the 1080: When my Rift first arrived I had my GTX970 installed, with DCS options set to 4K, a pixel density of 1.8 and everything maxed out except 'vertical sync' my frame counter recorded a rate of an average 28 FPS. However, when my Gainward 1080 arrived the framerate more than doubled. On average now I get approximately, 48-50 FPS. In closing, I do expect ED to implement the GTX1080 features, sooner rather than later.

AH, okay, we need to qualify the subject header, this fix is in relation to the OP, NOT the so-called 'yellow splodge', the fix is for the sort of corruption as shown in the OP image. We will continue seeking a cure for the Dreaded Lesser Yellow Splodge. :smilewink:

You sir, are a genius and a scholar, I will report this to the devs as a FIX. EDIT. First of all, I'd like to thanks subscriber JaBog32 for this amazing fix. This issue occurs only when the user right clicks desktop 'personalize' then 'display' and selects 'let me choose one scaling level for all my displays' and only then if the size selected is above 125%, If the user selects instead 'change the size of all items' the pointer remains unaffected. So in conclusion: Reduce your font size to no more than 125% or set your display to 'change the size of all items' until ED provides scalable fonts in the VR GUI.

:thumbup::music_whistling: