Lange_666

Mapkey( &Throttle, IDLERON, PULSE+DX87); PULSE in capital letters

Honestly, just to get some VR going, needing to run WMR for Windows, WMR for Steam, SteamVR and the bulk of Steam settings and upscaling and downscaling and what not other crap is not the road to go if you ask me. No G2 or one of those WMR/Steam headsets for me, just way too much hassle. I'll stick with my Rift S.

For me it doesn't work either, when i enter a cockpit, first thing i do is reset the camera view and then adjust the cockpit camera view according to my liking. It changes for each aircraft. Saving these views never worked.

I use the INCR / DECR axis on my Warthog throttle for that. It works as a full zoom Axis in 2D and as a range "button" axis in VR. This way i can use the same function for both. In VR when the axis has a value below 50 , there is no zoom, when it reaches 50% it activates VR Zoom and it stays there until it reaches between 90% and 100% axis range, then it goes Spyglass Zoom (and back offcourse), works nice.

This one was one of the most disappointing flightsims i ever bought.

NP, just have fun...

I get an error because of the target.tmh is missing // ----------------------------------------------------------------------------- // Includes // ----------------------------------------------------------------------------- include "target.tmh" // Standard TM Header include "include/dx+.tmh" // DX++ Module include "include/pov.tmh" // Custom POV Hat module include "include/ldc.tmh" // LED Control module You have the above files in a separate directory called include For me this runs fine if i add target.tmh into the main directory (where main.tmc sits), it's missing. You can put that into the include folder if you want but then the first line needs to read: include "include/target.tmh" // Standard TM Header If i then run the script it works but with only 86 buttons (see below) Running script: J:\Backup\Hardware\Controllers\Target\Scripts\TM Warthog Universal HID_edited\main.tmc *** Allocated ProcInstances found from the previous run: use FreeProcInstance() *** Mapped plugin module "E:\Hardware\Target\TARGET\Plugins\sys.dll" Compile Succeeded. Physical USB HID devices managed by script! Currently plugged USB HID devices[2]: 1: "Throttle - HOTAS Warthog" - "USB\VID_044F&PID_0404&REV_0100" 2: "RIGHT VPC Stick TMW Grip" - "USB\VID_044F&PID_0402&REV_0001" USB HID device "Throttle - HOTAS Warthog"(USB\VID_044F&PID_0404\6&2DDD0237&0&3) selected USB HID device "RIGHT VPC Stick TMW Grip"(USB\VID_044F&PID_0402\7&15079D9&0&4) selected Virtual HID devices managed by script! Connecting virtual joystick...Done Device name set to Thrustmaster Combined Device created using DX+ Module with 86 buttons Standard POV Hat emulated on Joystick H3 Button-Controlled LED Module enabled main returned 0 86 DX buttons solution: Your main.tmc has this: // ------------------------- Event Callback Init ----------------------------- // Even Callback Btn count Joystick only DXpInit( &EventHandle, 86, CREATE_JOYSTICK); Change that 86 value to 120 to get 120 DX buttons. If i run the script then I then get this: Running script: J:\Backup\Hardware\Controllers\Target\Scripts\TM Warthog Universal HID_edited\main.tmc Mapped plugin module "E:\Hardware\Target\TARGET\Plugins\sys.dll" Compile Succeeded. Physical USB HID devices managed by script! Currently plugged USB HID devices[2]: 1: "Throttle - HOTAS Warthog" - "USB\VID_044F&PID_0404&REV_0100" 2: "RIGHT VPC Stick TMW Grip" - "USB\VID_044F&PID_0402&REV_0001" USB HID device "Throttle - HOTAS Warthog"(USB\VID_044F&PID_0404\6&2DDD0237&0&3) selected USB HID device "RIGHT VPC Stick TMW Grip"(USB\VID_044F&PID_0402\7&15079D9&0&4) selected Virtual HID devices managed by script! Connecting virtual joystick...Done Device name set to Thrustmaster Combined Device created using DX+ Module with 120 buttons Standard POV Hat emulated on Joystick H3 Button-Controlled LED Module enabled main returned 0 Button count in DCS goes to 99, the buttons from 100 to 120 reside just below button 1 in the list... Info: The RIGHT VPC Stick comes from the fact that i changed my Warthog stick base to a Virpil base and renamed the VID.

just attach your main.tcm file. Also, i see that in your example just above the lines you added are underlined....?

I guess you don't have enough space on your drive to install the game. My stable install goes over 250GB when installed (80% of the modules + 5 maps). It needs room to put the downloaded files and room to unpack these during installation.

attach your script (complete file), i'll take a look

You don't seem to have IDLERON IDLELON either in that script. You can place the anywhere. For easy lookup i would place then in the Throttle Engine section just above Axis Mapping. Also, DX50 and DX51 are already in use on the Boat Switch, so you have to give them another number above 86. // Throttle Idle On/OFF MapKey( &Throttle, IDLERON, PULSE+DX87); MapKey( &Throttle, IDLEROFF, PULSE+DX88); MapKey( &Throttle, IDLELON, PULSE+DX89); MapKey( &Throttle, IDLELOFF, PULSE+DX90); (The PULSE command will only briefly active (once) the switch, remove it if you want to keep it active the entire time the switch is activated). I don't know out of my head if the On or OFF switch on IDLE is the one that gets activated. If it doesn't work for ON or OFF you can always replace the one that does not work with: Example: if the OFF doesn't work, use MapKeyR (R from reverse) on the one that does work). MapKey( &Throttle, IDLERON, PULSE+DX87); MapKeyR( &Throttle, IDLERON, PULSE+DX88);

You can add them: MapKey(&Throttle, IDLEROFF, PULSE+DX50); MapKey(&Throttle, IDLELOFF, PULSE+DX51);

I like the Huey in VR (also have KA-50 but it's been ages since that engine ran). It's slow nature makes it perfect for low flying. The trees clip and twist bit but that's about it. And as Lurker and ShaunX say, the depth perception is phenomenal. I struggle a bit with landing helo's in 2D, it's never pretty but in VR it's a total different story, as smooth as a baby's ass...

Target script ain't that difficult, it's powerfull and really no need to be a programmer. The main part of the script are the buttons and switches, all the rest you can forget. Just work your way through the manual, step by step and run some stuff in the manual as you go. Just my 2 cents (and don't use somebody else's userfile for a HOTAS, in general it's not what you want anyway.

Under the app settings tab you can name them directly:

Please keep the presets, they have one big advantage over the ingame presets. Example: In game preset 1: VSync On In game preset 2: VSync Off The game always boots with the last preset set. If it's preset 1 with VSync ON and i then choose preset 2, DCS will restart to make the change. However, if i load DCS through the Updater Utility and select a preset, it will directly load the one i want without the need of a restart in case like a VSync switch.

If you never used a HOTAS then the Warthog gimbal might do the job because you don't know any better (but honestly, even a cheap joystick moves a lot better then Warthog gimbal imo). Coming from a Uber modded TM Cougar the Warthog gimbal just sucked, even when it felt a lot better the the original Cougar gimbal. Once you go the decent gimbal road (Virpil, VKB...) there is now way you will return to the original Warthog gimbal. As mentioned above, same can be said about the slew control. I changed mine with a Deltasim one. No return there either.

Warthog throttle is OK, stick gimbals are not (coming from a frictionless modded TM Cougar). I replaced the gimbal main spring first, then did some other modding and sanding + re-greasing. Still a no go for my taste. Replaced the TM Warthog stick base with a Virpil WarBRD one and placed the TM stick on that one, i'm a happy camper.

Ah, i didn't know about the change in approach. My biggest gripe in all this is that now the main DCS screen on a multi-monitor setup (where only one monitor is used for DCS and the other for docs) goes minimized the moment you click on the second monitor. Plain annoying if you ask me. But it still worked pre-2.7 so the change was made within DCS.

I play flightsims since the beginning of dawn and since then and with my hardware i'm almost always racing behind the software development and certainly so in flightsims. Instead of going for max settings and get teased on how good it can look, i now start the other other way, i put everything on low and then up it step by step until it reaches a breaking point (for me, dips below 60FPS in 2D, 40 FPS in VR) and then i take a step back to smooth it out. But I just keep wondering how software developers run/test their games if top notch hardware is not able to run it at max setting?

Check out the input/output section of the forum: https://forums.eagle.ru/forum/70-input-and-output/

I've asked this before and got no answer. Before full screen was full screen, since 2.7 i have no clue what i'm looking at when full screen is ticked. Alt-enter seems to switch between full screen and borderless window but after a few taps of these i'm lost and i have no clue what i'm looking at, full screen or borderless. @MAXsenna: where do you turn that FPS counter on in nVidia and how do you see the difference between full screen and borderless with it? Or do you just look at the FPS values for determination?

That's true but then Skatezilla's app delivers so much more then the switch between VR and noVR.

That's done intentionally to remind you how great they looked back then.

Since 2.7 full screen isn't full screen any more but windows borderless mode (which is still a window). Time to bring it back...