Vannipo

Haha, I just wanted to open a thread right now, where I wanted to ask: Is it possible to get AI Viggens to attack ships with RB-04/15 (AI-Version)? Cause I am trying and trying, but my AI Viggens won't attack the ships. Maybe it's just not possible right now, and I'm wasting lifetime again by finding out, whether this feature is missing or it's just me. :)

Yeah, but we have to be creative to get some bugs "workarounded"

And the gears should break at departures?

Feature Request: Pls let me (us) do all the Menue-Mission-Editor-Stuff without VR. And, if I click on "Fly", i put on my HMD. After changing many tiny things in the ME, my eyes already need a break.

Just that the FOV of ur eyes is fixed. But I know, what u meant.

default: LAlt+C But it should hide automaticly, if u dont move ur mouse.

Cause I didnt used it until now and have set it up, and mostly (late in the afternoon) I can't talk that loud, cause of my wife is sleeping early :D And yes, for immersion this would be perfect !

When switching between weapon systems or, i have to adjust my head position all the time while fyling, that I am able to see all infos in the HUD. Put the view-controls on e.g. RShift+RCtrl+JoystickPOV-Hat. Then its ez to adjust while in fights.

That even happens, when taking off. That even happens, when rolling on gras. That even happens, when touching the ground too hard. Any 4th landing I get stuck in the ground. I am not sure, whether HB integrated a suspension system. Absorbing bumps. But, these heavy bounces @take off... I am not sure, but I thnk that would break my neck in reality. I hope they fix/improve that.

Ich kenne es von anderen Foren so, dass man Text markieren kann, mit der Auswahl auf "Quote" klickt und nur den Text im Quote hat, der vorher markiert war.

Also, der Mauszeiger ist bei mir immer blau, wenn ich die Maus bewege. Wenn ich 2-3 Sekunden nichts damit mache, verschwindet der Mauszeiger wieder und ich sehe gar keinen. Einen normalen Mauszeiger sehe ich nur, wenn ich das ComMenü aktiv habe. Unter jedem Modul gibt es den Befehl "Per Maus klickbare Cockpitschalter AN/AUS" (Normalerweise ALT+C) Versuche es mal damit. Also, eigentlich möchte man, dass der Mauszeiger blau ist.

Until ED give us hotkeys... maybe yes. Funny :D More FOV for ur eyes. It thought, it's fixed by nature.

Yeah, that all can be. But what can't be, is: Starting a mission in the air with A0 and TV initialized. Then, the mission starts with an own position fix, I think, and ur NAV is broken until u re-fix it. And the DEVS need to avoid, that that can happen. So, @missionstart T0 musst be set. BTW: Deleting fixes as described in the manual, dont work for me. IMPORANT: Dont use the hotkey-command "TV Fix". Use "TV Fix (3 position-switch)". Then it comes 100% back to T0. And u dont leave the mission in TV.

yeah, 5 threads below ur new thread concerning the same. Here's a workaround, until we get a brake fix. Works nice. I just have clutch, brake and gas under my desk :) and I brake just with my brake pedal https://forums.eagle.ru/showpost.php?p=3437851&postcount=15

Sadly, no reaction from ED about this?

Its ok for me, if u want to use a mouse in a cockpit. I use it, too. But not for Com. I don't like and it destroys my immersion. I don't want to leave my stick for navigating through com menuesin the upper right corner. And it's really nothing special about it, to let the user map these commands above.

Exactly. I can explain it more clearly: I press the hotkey for com. Why I cant just now select the com items with my e.g. 8-way on my joystick? Maybe with pressing a modifyer key additionally. That I can decide. We just need mapable commands like: Com Menue Up (POV up) Com Menue Down (POV down) Com Menue Back (POV left) Com Menue Select (POV right) I just cant get it into my brain, why this possibility just doesn't even exists :D In nearly any system on earth, where u have a stick, u can act like this. Its just intuitive. Finding F1-F12 in fight and maybe in VR... No good idea But doing combos with the joystick like: "Down->Right->Down->Down->Right" is easy. Regards Vannipo

U really think that is a good idea? U really should implement selecting com items with joystick buttons. Cursor down, up, back, select. Just let us assign it to hotkeys. I have no time for leaving my stick alone for using my mouse in the cockpit for communcation. Pls have more good ideas. Like the idea of configurable modyfier keys. This is one of the best ideas on earth. :) Thanks in advance! Vannipo

Hey ED-Team, pls add a color gain/brightness/offset slider to the VR-section or have a look in your render-engine. That we VR users can get rid of these pushed RGB-Values to 4, which causes night missions has to be flown with this green/red/grey haze everywhere where it is dark. Pls allow RGB Values of 0. Then VR night flying will be fun. Explained in this post. Thank u very much.

What u say is kinda of logical (miss)conclusion and mixing up words... Zoom is based on FOV...? Strange... Sure it is. It is that. "Zoom" is just a word for making a FOV smaller. So it changes while zooming. Of Course if I zoom, I change the FOV. Cause that's what happens. If I hit the VR Zoom Button, I change the FOV of each Eye from 110° to an unnatural one. Like wacthing through binoculars. And the question is, whether it is possible to change that minimum FOV which DCS offers me by default. Thanks for the Num5 hint! Regards Vannipo

Hey Guys, which script I have to edit, to make the VR Zoom closer? Cause I mean, playing in 2D allows to zoom in much more and see more details. And if flying the Viggen and trying to lock targets, a closer zoom would be nice! And, is there a way to remove Num5 from recentering the head? I removed it anywhere I found Num 5 assigned in the settings, but it still remains, that I have to press Num5. Regards. Vannipo

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.

It doesnt work for me, too. Win7-64, GTX1080Ti

I (and maybe other, too) need the possibilty to rotate the data panel selector knob CW or CCW. Right now, I have to set 7 hotkeys for being able to switch it around. Additionally, it would be nice, if u add the possibilty to rotate all rotating knobs via axes.

That all concerns people, who dont have a 3 way switch. Where one of these buttons are not pressed @mission start