SVgamer72

For what it's worth I just tested on my WH base, and my VFX buttons work. So it is compatible.

The vast majority of throttles sold over the last couple of decades didn’t have detents. Those that did/do were not sold in great numbers. CH Pro Throttle - no detent Saitek X55/56 - no detent TM TWCS - no detent * Logitech G940 - no detents (it kind of had them, but they failed within days/weeks of use) * Virpil T-50 V3 - no detent * *Virpil T-50CM2 - no detent * Saitek X55F - detent TM Cougar/TQS - detent TM Warthog - detent * Virpil T-50 V1/V2 - detent * not sold in large numbers ** will be sold in greater numbers over time assuming another design doesn’t replace it. With the exception of the short lived Virpil V1/V2, only TM or a relatively few X65f owners who ponied up the cash for the high end kit got to play with detents. While it is disappointing that detents were removed from the newer design, that is an odd line to draw writing off arguably one of the best options offered to flight simmers. All is not lost...The Hornet and Viper use mappable throttle lifts, and you can create a virtual detent for other jets in the Virpil software. Mine is mapped to the shift key at 79.5% which is perfect for the F-14. My left hand still executes an action (button press vs lifting/pushing through on my modded WH) to effect a detent. Personally I lost a little and gained a lot more functionality across the board upgrading to the CM2. I now have 8 axes (6 physical and 2 virtual) with zoom literally at my finger tips. I finally have radar elevation and range which has been missing since upgrading from a TM cougar years ago. The additional 5way hats are icing on the cake filling in even more gaps in DCS while only sacrificing physical detents. In addition 3D printable plans for finger lift detents already exist for the Virpil V3, and it is likely only a matter of time before the same option exists for the CM2 (it might already exist and I just missed it). So it will likely be possible to have your cake and eat it too. Cheers. Sent from my iPhone using Tapatalk

In short it’s amazing. Coming from a Warthog it is a big step up. While not perfect, it’s darn close. User overview: Virtual Detents (since the physical were removed...best channel for Virpil software tutorials) Sent from my iPhone using Tapatalk

Congrats!!! Love your work. Sent from my iPhone using Tapatalk

In the control settings there is a “modifier” button on the lower left. When you open it there are 2 windows (left and right). The left side is for modifiers that work when a button is held and the right is a toggle (press to turn on and press again to turn off). Make sure your modifier is setup in the left window and not the right if you want it to work when the button is held. Sent from my iPhone using Tapatalk

It sounds like you have another axis mapped to thrust competing with the throttle for input. Check and see if thrust is mapped to more than 1 controller. Sent from my iPhone using Tapatalk

The one I am currently flying... I agree with you that once mastering the Tomcat (with auto wing sweep enabled), all the rest are much easier. Overall I am much better with a boom than a basket.

I would add that a used 1080ti (which has 11Gb of memory is worth considering if you are crunching the numbers to get the most bang for the buck.

I am not sure how to do it with Saitek software, but it is done pretty easily with a combo of vJoy and Joystick Gremlin. It is a very powerful and easy to use tool that can really enhance and pick up where native tools leave off. https://whitemagic.github.io/JoystickGremlin/interface/ Tempo: This container holds two groups of actions that get executed under different conditions. The first one is run when the input is pressed for a duration shorter then the specified delay. The second group is run when the input is pressed for longer then the specified delay. Whether the first group is executed with the input being pressed or only when it is released can be controlled by the activation setting.

When reporting a bug, it is best to offer a way or reproducing it for ED to look into. I am just presenting a repeatable way of seeing the bug observed on my system.

I see the same thing with the F-14. Toe brakes are at 50% when air starting. (enter mission and press rctrl+ent to see control inputs with hands and feet off controls). A small tap and they go back to zero. Sent from my iPhone using Tapatalk

Got a Fender part number? I have an ailing Cougar I gave up on due to parts not being available. Sent from my iPhone using Tapatalk

Happy to help! DCS does not make it easy to do common config mods. It would be nice if they built in a GUI tool to build the LUA files sort of like a mission editor.

I used one a few years ago with an Alienware 17r3 Laptop (built-in 980m, Graphics Amplifier with a GTX1070). It took some tweaking and messing around with Dell drivers to get it working, but once setup it ran faster/better as expected. 1. If you go this route, you want to research the bandwidth to the external card. You want throughput and performance on par with a PC where the card is plugged into a motherboard. 2. Make sure the driver support is solid from the laptop maker. 3. Make sure you have adequate cooling. Running DCS on a laptop is going to really push the laptop internals and could result in thermal throttling (reduced performance)

In case you were not aware, the TM MFDs do not have screens in the center. If you have a second monitor you can export the MFD screens and see how much of a difference it makes. You don't need to buy the MFD controls first.

I should have looked closer at your code snippet.... Swap your x and Y values for the Right MFD and set the Shkval dimensions to fit within the display size of the second monitor or less. You currently have it set to display below and off the screen. RIGHT_MFCD = { x = 2561; (starting where the first monitor ends and the second begins) y = 0; (starting at the top edge of the monitor - MAKE SURE BOTH ARE ALIGNED AT THE TOP WITH NO GAP IN WINDOWS) width = 1920; (Width of the second monitor) height = 1080; (height of the second monitor) }

Try changing the last line to this: GU_MAIN_VIEWPORT = Viewports.Center Also it should be RIGHT_MFCD by default as this was changed a while back (not sure when)

It sounds like you are close. It is going to take some tweaking. Hopefully a picture will help. Your numbers will be different based on your monitor WxH settings for each display device. 1. Validate the WxH settings and position for each monitor in windows, and make sure you have the right math. 2. Important: aligning all 3 displays across the top extends the total width only. It does NOT extend the total height, because montiors 2 and 3 are small than monitor 1.

***No payment needed if it works. Just pay it forward if you can help another DCS player someday*** 1. Set the 3 screens with left to right like this in Windows with the tops all even = 50+8+8 2. Main viewport/center will be your 50in resolution (X=0/Y=0 and w=3840/h=2160) 3. LMFD will start at the far right top corner value of the 50in (x=3840/Y=0) 4. RMFD will start at the top left corner value of the 50in+LMFD (x=4640/Y=0) 5. MFD size (w/h) would be the area of the MFDs (you will likely have to tweak this) 6. In DCS settings set the resolution to the highest value shown (50+8+8 for width, and 50 for height should be available or 5440x2160) 7. Select the lua file. It should be in the drop down list if saved to <DCS path>\Config\MonitorSetup\filename.lua (It will use the description in the file like below "MFDs on 8in screens" if you use the file I provided) Try the attached file 042020_Monitor+MFDs.lua

Flaming Cliffs 3 (if you are happy with the Su25T non-clickable cockpit) is the best bang for the buck due to the number of planes you get. For a fully clickable cockpit, a lot depends on the type of flying you want to do. All modules have a degree of complexity that requires patience, and muscle memory to learn the workflows and steps. So your best bet is to buy a module that you personally are drawn to that can perform the tasks you are interested in (A2A, A2G, Carrier Ops, etc)

My experience as well. He loses lock at a bugged or abnormally stupid level. I get not making him super human, but Jester is worse than having an empty backseat when it counts the most. He makes the constant vertical looping AI look like members of Mensa when it is Phoenix time. Still won’t stop flying and recommending the Tomcat despite the bugs. It is still so amazing despite flaws that will eventually get fixed. I might need a 12 step program... Sent from my iPhone using Tapatalk

When you calibrate the Throttle in Windows do you see the stick axis move? Did you map the X/Y CH Throttle axis in DCS to the TDC?

I have mine for about 1.5 weeks now. I love it!! The criticisms are valid, but they do not really take away from the experience when flying the DCS F-14 for me. The VFX works great on any module that doesn't benefit from or require multiple hats. I have mapped and used it successfully on all warbirds, F-86, MiG-15/19/21, F-5, L-39, Viggen, etc. It is easily mapped with a little creativity. For example you can use the weapon selector for the Dogfight Fwd/Center/Aft on the F-5E, and to cycle the weapons on the MiG-19 (rockets, guns, bombs, missiles).

Stay safe and healthy! You do amazing work, and it is very much appreciated.

Stable as long as you don't hamfist the controls. It will depart (adverse yaw), and rip the external stores off if you pull to many Gs. It feels like a faster, heavier, and less agile MiG-15 (as it should).