Lange_666

So SteamVR is mandatory? Not possible to circumvent this?

Beyond Visual Range

In the mission editor you can set the level of AI. null

1: Yes, the stick isn't properly balanced on it's center line. The heavy TM spring and friction of the plastic TM gimbals compensate for this but that is not a nice solution if you ask me. 2: I guess so, if you mount the front of the plate a bit upwarts it will compensate. With the stock springs, those that were mounted when the base arrived, the forward lean was quite prominent, way too much to my liking. With the provided heavy's, that lean is almost gone. That there is a slight amount of lean is not a big problem, you pull a lot more on the stick over a longer range then you push it. With the stock springs mounted, it was +/- like this: With the supplied heavy springs it became this: I'm sure that with the separate to buy extra heavy's the lean is totally gone. Opening the base up and change the cams or springs isn't much of a hassle. Piece of cake.

If going for a Virpil WarBRD base take note of the following: - You can rewrite the USB/VID number of the WarBRD if you put a TM stick on it which then can acts like a Warthog Stick inside the TM Target software (if you should use that). - The WarBRD sticks are made of plastic weighing a lot less then your old TM stick you will put on the WarBRD base. This means it leans forward with the stock springs that are mounted. However, it comes with a set of heavier springs. If installed the stick forward lean is then reduced to around 2° or less. A thing you won't notice once calibrated. If needed, you can always order a set of extra heavy springs sold separately to overcome that last 2° lean. But i feel it's a waste of money. - The WarBRD base can be fitted with a number of cams, i use those with zero center feel/bump. - If you tend to sell the Warthog base, sell it without the base plate (there is demand for that, i sold mine within 48 hours). Then swap the Virpil base plate out for the TM one (you have to drill 4 new holes to in the TM base plate to fit the Virpil base on it, no worries, the old holes are covered by the new base). After that... if you are used to a TM gimbal, you're just gonna be spoiled (as if you would with a VKB one).

You could have saved yourself the effort. This is one you can't win.

The moment i went to PC gaming (coming from Commodore VIC-20, C-64 and Amiga) i started chasing and i still do this to this day. Nothing has changed since then (sort of).

Core speed doesn't say everything. What the 5800X3D really makes it shine is it's 96MB level 3 cache.

Anything Virpil, VKB or WinWing or a combo of these. Sidenote: What i have: TM Warthog but i switched out the Warthog stick base for a Virpil WarBRD one, way better, no friction (i used to have a TM Cougar with a Ubermod as gimbal for the stick so the base Warthog gimbal didn't cut it after using that). I do like the WH throttle.

Also, do a test run with everything off, hardware and software (and remove all exports and hooks, not only winwing), that is not DCS related (you also run a motion sim if i'm correct), run even without controllers (if needed, unhook them), just use the keyboard (make sure nothing runs in the background) and add your stuff bit by bit. Something is clogging up.

No (not for the Warthog), but there are a few posts about pinched wires here on the forum (and more on the net). (+ i have 38 years of experience (retired now) in electric/electronic maintenance/problem solving, things like this then still ring a little bell...) If it's the controller board it will (as good as) always happen when one or a certain combination of switches/buttons is activated, no matter what position the throttle is in. If you are sure that it's not a combination of switches/buttons that causes it to act up, it rules out the controller board (99%). If it are wires then it will probably happen when you move the throttle up to a certain point (a mm more forward or backward can be enough), if you don't use the switch then, nothing happens, if the switch which has pinched wires is activated, it could lead to short circuited input on your controller board giving weird results (without damaging the controller board, it just gets the wrong input). I have a refurbished Warthog (straight from TM) and because i did read that there could be problems with the wires inside the throttle, the first thing i did was to check if the wires didn't rub against anything that could lead to problems over time. They didn't.

Both. 2D: Overall high settings (with shadows off since 2.8), clouds to Ultra (even at Ultra settings, clouds in 2.8 don't look that good, specially around the edges), screens to 1024, MSAA x4, Anisotropic x16. VR: Medium to low, screens to 1024 for clarity, main reason for going lower is that i want to run with MSAA to x4 and Anisotropic to x16 to counter the high shimmering if ran without, same goes for clouds, set to Ultra since 2.8, otherwise they look ugly, certainly on the edges, compared to 2.7, used to be on standard with 2.7. On simple missions i can go quite a bit higher on settings but i keep them that way for more complex multiplayer missions where there is (a lot) more demand. I also cap the FPS to smooth everything out: - 60 in 2D, because i like to keep the FPS as steady as possible, if FPS fluctuates to much, TrackIR doesn't play nice on fast moving terrain. 120 would be nice to but i can't hold that across the board so the cap is 60. If TrackIR wouldn't be so picky on it's own pull rate, i would let the FPS do it's thing. - 40 in VR, (Rift-S = 80Hz) but here plays the same as with TrackIR, jumping FPS makes everything stutter. So i just ASW at 40Hz giving a steady 40FPS which makes it smooth, no stuttering. Never found fluctuating FPS a good thing, it's always visible when they jump around and i don't really care for low frametimes, not needed. The more steady they are, the smoother.

That's like getting pregnant without...

Just had a little test flight in the F-14. Everything fine and smooth (OB version)

It could be a controller board or a pinched wire (for this to see you have to open it up and even then it could be difficult to pinpoint), the switches itself causing this behavior is unlikely.

Same can be done with the 5800X3D.

That's an old one. More recent is to be found here: https://github.com/asherao/DCS-ExportScripts/tree/master/Scripts/DCS-ExportScript/ExportsModules But those are still individual files, i'm looking for one file with everything in it. Think i found the right tree in this Github jungle: https://github.com/asherao/DCS-ExportScripts/archive/refs/heads/master.zip

4090 Titan: https://www.guru3d.com/news-story/photo-of-alleged-rtx-4000-titan-prototype-shows-thick-heatsink-and-two-12vhpwr-connectors.html

Can somebody provide a "direct" download link to the DCS-ExportScript because i always end up on the main Github DCS ExportScript and then i'm lost... in the Github jungle. I never ever find the file or link that i need. Thx

Through Wifi or via a link cable? + i still like to know what the entire setup procedure is and what software is used (that was my original question).

I had issues with my headset (Rift-S) loosing position a lot when overall light changed with v44 Oculus software. This didn't happen before v44 of the Oculus software, on pre v44 it only happened from as good as dark to fully lit. With v46 of the software (they jumped from v44 to v46), they seemed to have corrected that loosing position 'bug' under v44. I guess you all are on v47 at the moment dealing again with the same problem that i had with v44. I'm still on v46 and i tend not to upgrade to v47 because of that (and because there's nothing in the updates for the Rift-S anyway anymore).

The F-16 (don't know about other aircraft) cheats a bit by changing stick input curves when the refuel door opens and sets this back to default when it closes. I didn't know about this and found out the hard way because i always backed off a bit after refueling, rolled 180° upside down and then pulled the stick to make a half loop. Sometimes i could not manage that loop and i would crash into the ground until i found out that the stick input changed with the refuel door open. With the door open, i was not able to make the half loop, with the door closed i even had plenty of room left. It was a bit of an A HA moment. Also, if you're using a standard Warthog stick base, friction could be a bit of problem for precise movement. Since i use Target Script for my stick profiles and since it's possible to change axis behavior with the script, i added the same principle for each of my aircraft profiles, making controlling the airplane a lot easier when refueling. I also set a LED to let me see in what axis state i'm in for in case i should forget. For the moment i have 3 curves. You could also integrate this at the same time with open/close of the refuel door/probe. SEQ( Change stick axis behaviour - open the sequence CHAIN( EXEC( // curve 1 "SetSCurve(&Joystick, JOYX, 0, 0, 0, 2, 0); SetSCurve(&Joystick, JOYY, 0, 0, 0, 2, 0);" ), LED(&Throttle, LED_ONOFF, LED_CURRENT+LED2), LED(&Throttle, LED_ONOFF, LED_CURRENT-LED4) ), CHAIN( EXEC( // curve 2 "SetSCurve(&Joystick, JOYX, 0, 0, 0, 4, 0); SetSCurve(&Joystick, JOYY, 0, 0, 0, 4, 0);" ), LED(&Throttle, LED_ONOFF, LED_CURRENT+LED4), LED(&Throttle, LED_ONOFF, LED_CURRENT-LED2) ), CHAIN( EXEC( // reset to normal "SetSCurve(&Joystick, JOYX, 0, 0, 0 ,0, 0); SetSCurve(&Joystick, JOYY, 0, 0, 0 ,0, 0);" ), LED(&Throttle, LED_ONOFF, LED_CURRENT-LED2), LED(&Throttle, LED_ONOFF, LED_CURRENT-LED4) )), //close the Sequence

And the UH-1...

Any chance you can put the difference between the two in here?

https://forum.dcs.world/forum/302-virtual-reality/