BlackSharkAce

Hi, You can try this: https://vr4dcs.com/2020/12/24/how-to-nail-reverb-setup/ I also like this tool to set additional parameters: The there’s some good optimization tricks here: (previous videos by the same author also have some info, but may be outdated) With all this I’m getting mostly enjoyable 45fps with motion reprojection at steamVRSS 90%/PD1.0 on a 8700k/1080ti OC build.

4 cores is a bit tight indeed, I see your cpu and ram are quite “slow” compared to your GPU. Shader mods and such will help for sure, but can’t do magic.

I think reprojection is handled by steamVR. So you can set a different CPU affinity to those threads and not take away from the main game thread. Works in my end with a 8700k & 1080 ti @ 80% SS.

What I do is clamp my FPS to 45, then it’s constantly reprojecting and the workload levels out.

Amen my friend !

Did you try to uninstall your software / drivers and redo stall follow the instructions here: https://vr4dcs.com/2020/12/24/how-to-nail-reverb-setup/ ?

I can send some screenshots later, my steamVR @ 100% is 2800 or so in pixels.

You *should* be able to run higher settings in my experience if you’re willing to install some mods like « VR Shader » and « No Flat Shadows ». I’m running mostly 45+ FPS with reprojection in MP (BlueFlag server) @ PD 1 and SS 80% in SteamVR on a 1080Ti @ 1.9 GHz.

Maybe you can find some useful info here: https://vr4dcs.com/2020/12/24/how-to-nail-reverb-setup/ Best,

Even more odd, I get different pixel values on my G2 @ 100% then shown in these screenshots. Nearly the same, but like x3106 pixels or something like that.. Maybe it’s linked to the GPU ?

Thanks for this input ! I’m happily on the G2 train as well with a sweaty 1080Ti / 8700k. One question: How come your steamVR resolutions say 182% & 124% but the pixel counts are both under the native resolution for the G2 ? I get much higher values at 100%.. Best,

+1 for that question.

Agree, performance is slightly better and visuals are on the rise as well. What’s also on the rise is CTDs and bugged systems.

It’s beyond me at this point.. also stable version is basically a previous beta with the same bugs so can’t really use that either. I don’t understand why people keep defending ED. In the current crisis the first step is to acknowledge there is a profound issue in their development process. Loving the game, but suffering the lack of improvement and constant state of unfinished work. Hope they figure it out sooner then later. Cheers’

+1, happens during multiplayer as well. All of a sudden there is no more in-game sounds. Other windows sounds still work.

Let us know when / how you solve it :)

VPC Warbrd Base issue When moving from one end to the other check that the values are continuous, if there is a discontinuity, then try to activate the “offset” setting shown in the picture here-attached. Maybe also try to calibrate the axis and post a screenshot of the values (min, center, max) that could be interesting to understand if it is a software issue or an electronic sensing issue. I’ve had to enable the “offset” on one of my axis as well because the position would “overflow” somewhere in the range of motion.

Sounds like sensor value overflow, I think there is an option to offset the range in their software. Does it go to center exactly or to some opposite position ?

Hi all, I have been trying to find a solution to use the "zoom in" binding while also using TrackIR zoom. Contexte: I use TrackIR to slightly zoom in when looking down at my instruments. This caused an issue where I could not use the "zoom in" binding in DCS because the zoom would be overruled by the TrackIR zoom axis as I move my head. (Hope this makes sense ?) Goal: Being able to use my TrackIR zoom for small zoom level when looking at my instruments, and also be able to use the "zoom in" binding when looking for targets in the sky. Solution: TARGET settings for the "zoom in" button MapKey(&Joystick, H3R,CHAIN(DX28, DX12)); DCS input settings: Modifier DX28 Zoom in DX12 + [i]DX28[/i] Zoom axis TRACKIR_Z Some other axis TRACKIR_Z + [i]DX28[/i] The result is that, in normal conditions (when no modifier is pressed), all axis work as usual with TrackIR providing my instrument zoom. When I press H3R (DX12 + DX28), DCS is no longer using TRACKIR_Z for zooming because TRACKIR_Z + DX28 is assigned to some other axis, and zooms in since DX12 + DX28 is assigned to that keybind. This achieves my zoom for looking for targets in the sky. When I release H3R everything is back to normal. Hope this makes sense and can help someone else out =) Happy flying !

Issues with VPC tool March 20th One of the legacy profiles. WarBrD + TMW grip. Are the legacy profiles not supported anymore ? Here is the error message I get when trying to import the profile:

Hi, When trying to import a profile after updating my WarBrD base to the latest firmware I’m getting an error « trying to read beyond end of file ». I tried it in administrator mode aswell to no avail. I have no issues with older versions of the VPC tool. Anyone else having the same issue ? Any workarounds ? Best,

VKB Noob Questions - My Quest to replace my Warthog Gimbal Wrong ! You can use TARGET only for your stick and throttle. Including axis curves and deadzones. All you need to do is use the correct mode, PID & VID when configuring the base. I’ve done it and kept my TARGET script. Cheers,

Changing the defaults for Countermeasures I went this route if that is what you’re looking for: https://forums.eagle.ru/showpost.php?p=3655201&postcount=18 Cheers

I was wondering the same, found my answer in the wiki: https://wiki.hoggitworld.com/view/F/A-18C Youhou, reduced my inital setup routine :thumbup:

F-14 stream and purchase It’s on the dcs website under special offer.