Lange_666

Ok, nothing disabled. What about my 2 other questions?

Can you give some extra info on the phrase in red because i don't understand what you mean and how you "checked the driver and the window indication"? You mean it's still detected by the Windows Device manager? Any other game installed you can try the Warthog on? If you go to C:\Users\Your Name\Saved Games\DCS\Config\Input do you have a disabled.lua there (on the bottom of the list). If yes, what's in it?

They only offer rotor pedals according to their website. Links to their previous devices show empty.

I guess you can say that for a lot of headsets these days. Also i believe that that more and more headsets will go the wireless road. That's why i didn't get one yet, too much hassle to my liking to get it going (maybe i'm spoiled in this area with my Rift-S, start Oculus software and off you go) and the lack of display port.

@whitav8 really? Next time you ask a question my finger will the only thing you gonna get.

No, i subscribed for a test run on the MFG website. Milan wanted a test group of 30 people in the test run. The first ones i got for testing are the ones with the cutouts. Since i wanted an option to mount them lower, Milan made and send the ones with the 12 fixing holes. I have no idea what the other testers reported or what they got send as test pedals. I see that the ones with the cutouts didn't make into production, and the others i have never tried or seen. Mine don't have the MFG logo either. The ones i have resemble most to the grey ones: I'm also using a modified brake limiter set so i need to put less force on the pedals for braking. I have a set with an extended arm above the upper bolt with more holes for the spring to attach. Milan was so kind to make them on demand after i reported that i wanted to use less power for braking because using combat pedals requires a bit more force under braking compared to the ME109 pedals. I now see on the website that you can get a set of lighter springs instead.

These are the ones i have fitted: As you can compare with those on the MFG website, these have a lot more fixing holes in them. With these i can keep my heels on the floor and use my toes to brake. With the ME1009's i never could find a good setup. Below are the original test pedals i got from Milan, less fixing holes, these where still sitting a bit to high but due to the cutout's (which i really liked) it wasn't possible to lower them. Still have them laying around... PS: just discovered by moving the pedals from under my desk to take a photo: the bolts i used are not of a very good quality, the heads show rust. Guess i snapped the wrong ones from work.

I use combat style foot rests on my MFG (got them sended over by Milan for testing). The ones i have have a few more fixing holes in them to get the position i wanted. I didn't like the original ME109's.

The regular clip isn't made for that (should be clipped onto the cap of the baseball cap) but i guess you can stick it onto a headset too. The Pro clip is actually made to clip on the side of a headset as Silverdevil shows. I never got a Pro clip because at first they where very fragile, lots of reports that they broke quickly. Don't know the current state.

A BIG yes... been using it for years. Started of with a TIR 1, now have the TIR 4 already since release in 2006. Still works super after all these years. BIG BIG Pro: There is no way to go back to joystick or keyboard to look around once you used this. Minor Cons: - Need to wear a baseball cap to put the provided trackclip on or buy a separate Trackclip Pro but that last one hooks you up with a cable. - Sudden rays on sunlight can mess things up, certainly with the trackhat. Personal con: On fast moving terrain it can get a little stuttery due to the TrackIR pull rate not in sync with your FPS rate. You can avoid this by capping your FPS to the pullrate of the TrackIR (or a division of it). I cap my FPS to 60 and then it's a supersmooth ride. But not everybody sees this as a problem. There are other options too like Tobi Eye Tracker, a DIY setup with a webcam and OpenTrack software or a setup with your cell phone and face tracking but never tried any of these. Can't compare.

Just what is says: Control Indicator. It shows you your current control inputs (stick, throttle, rudder, trim).

Headtracking like TrackIR: https://www.trackir.com/, Tobi Eye Tracker: https://gaming.tobii.com/product/eye-tracker-5/ or DIY with a webcam and Open Track: https://github.com/opentrack/opentrack/releases

For the Cougar to run on a "modern" Windows: https://forum.dcs.world/topic/152816-hotas-cougar-software-on-a-modern-windows

FS2020 is all about eye-candy, the rest is just way below par. I take the crappy AI and ATC behavior as an example, it's just plain horrible for a game that calls itself a simulation.

If AI can deliver a 30% performance boost, real programmers should be able to deliver at least the same boost because they wrote the AI code in the first place.

Thx for the tip, should have thought of it myself. Turned out to be the F-16C lua (wondering: i have stutters when this lua is in the ExportsModules, shouldn't other people have them too, it's the latest version that is in the DCS ExportScript). For now: Removed the entire DCS-Exportscript since i don't export anything to the Streamdeck for my own profiles, they only work one way (Deck to DCS).

That was my thought too but how do you pinpoint what is causing that?

Yesterday i noticed a constant annoying stutter when running DCS. Before that it ran silky smooth. Quick test in IL-2 and Elite Dangerous showed that it was only in DCS because they ran supersmooth. Because i played around with my StreamDeck the other day (added an M-2000 profile and some HW64Info data) i first thought of that. Removed my export.lua and all ran smooth again. Then i commented out line by line to find the problem and it turned out to be the DCS-ExportScript entry. When i commented out: -- load the DCS ExportScript for DAC and Ikarus dofile(lfs.writedir()..[[Scripts\DCS-ExportScript\ExportScript.lua]]) DCS ran without stutters again. I also have TacView, The Way and SRS in the export.lua but these didn't cause stutters, only the DCS ExportScript did. Q1: What causes DCS to stutter with this DCS ExportScript (latest version) in the export.lua and how to prevent it? Q2: Do i actually need DCS-ExportScript for my StreamDeck. The profiles that i made still actually work without it.

It's one of the first things i would look into because you find so much problems with it when searching the net but on the other hand, it should not behave like you mentioned. I have iCUE running (HS70 Pro headphones (sound setup + battery level check) and H115i AIO (fan curves) and i don't see an FPS drop. Do you have anything RGB control running through iCUE?

These little connectors normally don't come loose in their seating. Any chance of the wires pulling to hard on it while moving the throttle?

And after reading all of this above, the already growing VR forest of trees grew into a dense VR jungle. I'll just stick to my Rift-S. Start Oculus software and done. Can't be simpler.

Yes you can... Controls: UI Layer: recenter VR headset

Pico 4 looked quite promising in the beginning but i'm not interrested/willing to run multiple interface program upon interface program, each with it's own interfering setups just to get the thing going. I ain't gonna go that road.