Einherjer

Wags post: #395 in this thread

Maybe on lase code 1113? ;) so the FACing Gazelle can lase targets for a-10c, su-25t or mod planes based on it Realism? As long we have no recon chopper we can fill this gap with creativity, phantasy and Mods

Thanks Pat! Oh if only the laser could be detectable by the A-10 ;)

Nice one! Will you release it?

Hehe - same here ;)

No radar - so no AMRAAM, but if the a/g radar is done by ed, the av-8b with radar will follow

A-10C Maverick Frage (Deutsch) Hier im forum, nicht unter English sondern international -> deutsch schauen

Warum benutzt du eigentlich nicht das deutsche unter forum?

Oh please, everybody shut up and delete this thread... And no word to ed! ;) I hope this bug is on the last place on the bug fix list... For ever on the last place...

Yeah that's similar to that, what I did (see above), I just shifted the fiewports out of the screens, works also. edit: Testet eye_shift left zero and doubled the eye_shift right -> looks absolutly the same (a few degrees rotation to the right, which is not noticable especially with head tracking) and the Mouse courser offset problem is solved!

That's what I did first - but the vanishing point of the projection still seems to be in the middle of the viewport, so 5.3 cm no matter what eye_shift I set (near objects are affected) But maybe I am just wrong - will test it this evening again

Will try it later, hope it will fix this issue.

Update : the viewDx parameter seems to be correlated with some kind of convergence, so that is not optimal for shifting the center of view. So, next try : I set my X coordinate for the left eye to -100 and for the right eye to screen size x 0.5 + 100, this gives me 200 pixels separation between both view ports - I can't see the separation with my headset but it works well now! Next thing to try : Setting eye_shift for the left eye to zero and double the right, maybe it affects the shift of the mouse cursor?!

I have no heavy impacts of the performance when rendering in stereo mode... It varied between 40 and 110fps on 1080p with a sandy bridge i5 and a gtx 770 - but I have to say I am not really sensible for motion sickness, so playing 2 hours with 40fps, some lags and a not linear head tracking is no problem for me ;)

Google cardboard with DCS world Can't use trinus, there is no version for ios atm. Setting up ipd on the cardboard doesn't really change the ipd of the image, just the lenses so on smaller smartphones this could be a problem. After 2 hours in a mission I have had this feeling. Now it's far better - when I let my focus shift between near and far scenes it feels more natural and all feels bigger not so toyish But now, zooming is another story... Need more tweaking Edit : is the viewDx parameter the shift of the center of view? Maybe I will try another solution with the viewport sizes... I have tried again something, I was on the home screen of my iPhone and put it into the freefly vr headset, shut one eye and look at the center of my view - straight ahead, then I shut the other eye and do the same - I was looking at the top of my notice app and with the other eye on the page indicator of the home screen - then I measured the distance between this 2 points and it was exactly my ipd.

I have a question because the ipd... When I render dcs in stereo for my iPhone6 (4,7") the distance between the left and right right center of view is 5,3 cm, but my ipd is 6,4 cm. So, with the cardboard on I always have to "cross eye" to focus on a distant object, and that makes my eyes tired. I have played around with the viewDx parameters in the stereo.lua I have set the eye_shift to zero and increased the viewDx (which I mean is the center of view, correct me if I'm wrong) for both eyes until the distant objects like clouds are separated by 6,4 cm. Then set my eye_shift back to the ipd wide and it feels... Better Has anyone done something similar yet? Greets

That's normal - you can edit the stereo.lua The ui is defined for the fiewport.left, but you can set coordinates also

Had the same problem - a new control device was added which automatically was bound to the default axis - just delete the axis category for the device and you are good to go

Oh this mouse pointer offset... Is there a solution yet?

We can also refuel from the carrier based Viking... The 3d model looks quite ugly but that's OK for me as long as it gives me my fuel ;)

Wow! Nice find!

What vr headsets are you using? I am searching for a new one for my iPhone with a bigger fov

L39 pit Absolutely, my rudder pedals are self made too, and I had planned toe brakes, but I like the Russian style of braking ;) and it's always good to have an additional axis

L39 pit Yes it moves a potentiometer - it's a very precise axis now for the wheelbrakes.

And I was searching for this profile in the geforce experience tool... My fault :)