Vannipo

Hi. The water level on the PG Map is too low. Or the landscape too high? Partly. :) Steep coastlines everywhere and I can see textures, which otherwise definetly belongs under water. Or maybe it's Work in Progress Regards

No, I think anybody has it, but just doesn't recognize it: The complete water level in PG-Map is too low. I see ground, which otherwise belongs under water everywhere.

Yes, I can "tdc" the IRMAV again, or the TV again, but I can't get the IRMAV following the TV again. And that's all about.

No, I tried. It's just not possible, that u can unlock the Maverick and bring it to TV mode again. You have to undesignate everything and start from zero. This is strange. And very unhandy.

Yes, a bit. But this is no solution. If u know, what gamma is doing, it just a curved multiplier. So, to get it black, u need to multiply it by 0. But, this not done by a gamma curve. You have to keep in mind: The Loading screen has NO haze. Why? There we all have 100% blacks. It's only in the game engine, which pushes (maybe just by a post tonemapping) the values up to 4 minimum.

Wow, so awesome! But I think u should buy a third sensor for Flightsims (or just DCS) only, and use this single one mounted on the chair. Really. Else u have double motion. And that makes no sense. U can see it in the vid. Did u try that out?

Hopefully, u use it with a modifier key, that u dont have to waste important buttons on a joystick for mouse functions...

Keep in mind how the VPC Software works. U dont even need a driver for your stick. You load the burned information from the joystick. U change values... maybe load a new profile... maybe calibrate your axis by just moving them all around.. ...and all of this stuff you burn back to the joysticks firmware. And u never need the VPC again. If u don't want to change something.

Yes, I can reproduce it. Seems, u found a new bug. :thumbup: Thanks for just uploading ur mission. Btw, wrong sub forum.

Still 2 84X.

In any mission u choose? Maybe try a repair.

I analyzed a screenshot, which i made at night and checked the colors. The darkest color value I found (in the night sky), is: R 4 G 4 B 4 With an ingame gamma of 2.0. So, DCS has NO 100% blacks in the rendered image. And thats why, we all have this red/green/grey haze. The Oculus pushes these low values a bit, that we are able to see low values. But this makes this haze in DCS. So, if the DCS render engine image output would be re-offsetted, we all would have a great night VR flight experience. Or just the whole range from zero should be used. Like in the loading screen, where u have a 100% black environment and NO haze, while loading and moving the head around. Noone has haze there. It's up to the DEVS to fix this RGB "offset". Either the gamma calcualtion is incorrect, or they shift the picture before applying the gamma curve. A gamma curve keeps zero values untouched. If the values would be 100% black before applying the gamma, they stay 100% black. If u pull down the gamma as much as possible, the haze dissappears. Is there a way to adjust RGB-curves for the oculus output? Or what the Oculus receives? Regards Vannipo Even a Screenshot made in 2D shows the offseted luminance. It's not pushed by the oculus itself. Maybe an NVidia Problem? Or just the render-engine of DCS.

BTW, this issue could be fixed within 10 minutes, if u know, where to tweak which values. ED...

Attach the mission, and someone (maybe me) can have a closer look. This is faster than finding out, what could be wrong. In the first step. Why u postet in VR Forum? Is it a VR problem to u? Does it happen, if u fly in 2D?

I analyzed a screenshot, which i made at night and checked the colors. The darkest color value I found (in the night sky), is: R 4 G 4 B 4 With an ingame gamma of 2.0. So, DCS has NO 100% blacks in the rendered image. And thats why, we all have this red/green/grey haze. The Oculus pushes these low values a bit, that we are able to see low values. But this makes this haze in DCS. So, if the DCS render engine image output would be re-offsetted, we all would have a great night VR flight experience. Or just the whole range from zero should be used. Like in the loading screen, where u have a 100% black environment and NO haze, while loading and moving the head around. Noone has haze there. It's up to the DEVS to fix this RGB "offset". Either the gamma calcualtion is incorrect, or they shift the picture before applying the gamma curve. A gamma curve keeps zero values untouched. If the values would be 100% black before applying the gamma, they stay 100% black. If u pull down the gamma as much as possible, the haze dissappears. Is there a way to adjust RGB-curves for the oculus output? Or what the Oculus receives? Regards Vannipo Even a Screenshot made in 2D shows the offseted luminance. It's not pushed by the oculus itself. Maybe an NVidia Problem? Or just the render-engine of DCS.

UCR Rulez. Yes, I just loaded the default profiles in the VPC Software one time, calibrated, saved it and never opened the software again. The Brake lever is already a button, too. So... UCR for the rest. I like it, that u dont have a driver for the Virpil products. Ur burn all information for a default windows joystick to the firmware. That is awesome!

Yes, that's why I said: I just wanted to be sure, that there is no button, which is e.g. a 5 way hat, that doesn't work properly on my stick. Yeah, I don't care the numbers, too. I press the button ingame. Done. Thanks!

Nono, I just said, that a guy, who is asking for a good throttle, has to keep the resolution in mind, cause it - in my opinion (I recognized a difference) - matters a lot. That was my first post. Nothing more or less. It's ok for me, if u have ur opinion. My opinion comes out of my experience with both systems. That concerns sticks more, but also throttles. And no, I am not against CH Products. No way. They are very precise. I am complaining about 8-bit axes. And CH Products just use it.

Yes, that's why i asked for other titles. We will see. Mostly, if u don't hear anything again, the problem may be solved by himself :)

Thanks.

I just dont understand, why I have to use my HMDR in the menues? Why ED just doesn't let me do the menue stuff on my 2D-monitor, and just before in the cockpit, I put on my HMDR and use it only, while in the aircraft. To do MissionEditor stuff with an e.g. Oculus is... causing eye cancer, so, I start DCS in 2D, make all my changes, restart it in VR, just to prevent my eyes of being used too much in VR before the flight... I don't know, it works in other titles... all except the sim itself is adjustable on the monitor. But, nice work, btw...

You dont have to map that. It is "Num5" at any time. ------- So, do u have the problem in other titles?

In the most cases his system doesn't even reach 60fps. Or 45. ... Someone knows, why he sais that there is no difference in fps between the 5K and 8K?

12" throttle travel? Noone talked about that. I talked about 12 STEPS. Not inches. No length. U really have to read and understand exactly. Just for u again to understand: It doesnt matter, how long the travel is. If u have only 256 steps, u have 12 steps (256 / 20) in the first 5% travel. And this is too less. In some machines you need a fine ajustment in these 5% travel. And with 8-bit u are too rough. Fly with an 8-bit throttle. No problem. U have to know. I know the HUGE difference. You may not. But its ok for me. Take this hint or just let it be. There must be a reason, why there are 16-bit throttles and clutches and gas pedals and brake pedals. U don't think so? Then keep your 8-bit and think, this one is fine enough :thumbup: Dont buy e.g. a CH-Throttle. Only buy throttles with a higher resolution is my hint.

+1, I made a thread for this hotkey, too :) but pls dont put it in any thread :thumbup: