Teej

Asking strictly out of curiosity, did you/they check the engine rotation as I had been commenting on? [Actual FM engine simulation feeding that gyro - I'm well aware the animation could've been different) Again - curiosity since the direction of the yaw suggests anticlockwise engine spin.

Excellent news, NineLine. Can't wait to see it!

Thanks, I will take a look. However before I do let me make some things 100% clear. 1: It is not in any way dependent on input method. I can reproduce it with keyboard, moving stick or FSSB R3L. There is nothing special in DCS for FSSB. Yes, it “feels right” because the (real) viper was designed to be flown with a force input and there may be FLCS code within DCS that mimics the function of the real bird. Regardless, that is definitely not the problem here. 2: Your roll control setting is quite simple - it reduces how much roll the pilot can input with THAT device while pitch is input. As in if you’re pulling more than a small amount on the stick, your roll input is capped at ~25%. That cannot help here as the problem is not due to pilot inputting roll. This is coming from an intentional act by ED developers. If RCA were the answer I would happily create and release some custom code to do this with _any_ stick and release it for everyone. Wouldn’t take but an hour or two. But it won’t help. 3: The reason it’s a big deal to Panic and not to you is he is flying formation aerobatics - holding a sight picture with a lead jet while close enough to overlap several feet of wing with the jet he’s following - the leader’s wingtip is closer to Panic’s canopy than Panic’s own wingtip. Having your jet make uncommanded and unrealistic movement is the problem. 4: The other reason RCA won’t help is Panic, like the Thunderbirds, is flying with full “nose down” trim. That means even flying flat and level, the stick is pulled back far enough that RCA would cause him to have to use much larger roll inputs to hold paint, and full roll authority isn’t even an option (with RCA). The key things here are that this is resulting from a deliberate FM configuration by ED that cannot be mitigated by choice of input method. If as Nineline said this is coming from modeling the gyroscopic precession of the engine, then it’s in the wrong direction, as if they modeled an engine spinning the other way. Regardless, the magnitude is suspiciously high. If it’s going to be modeled, it should be modeling a very slight right yaw moment.

For that explanation....the effect is backwards. The F-16's engines (regardless of block) spin "clockwise" when viewed from the rear - as does every turbine GE and PW make (Rolls is the opposite. Wouldn't be surprised if Russian derived are as well). If you apply a nose-up force (positive pitch) to something spinning like that, the gyroscopic precession that results is a yaw to the right. The engine also spins the wrong way graphically in the sim, so at least that's a consistent error. Tailwheel pilots experience the reverse of this - when you push the nose down to raise the tail, that adds to the prop plane's left turning tendency. When you compare an F-16 to a P-51, for example, the resultant effects on the plane from gyroscopic precession should be much much smaller. The rotational inertia of the engine is about 10x as large (smaller diameter of heavy rotating parts, but at a higher velocity). On the other hand the plane has about 100x the rotational inertia...so the net force on the airframe should be on the order of 1/10 what it was on a WW2 fighter.

Hey, Raven... I have an R3L and would be curious to see your settings, but let me make some comments here too.... I am saying the following NOT as any kind of flex, just to put my comments in perspective. 1: I am a (private) pilot - but not of any jet, let alone a Viper. I fly an RV-10. 2: I have a good background in controls and control theory. ~ 15 years ago I designed and successfully implemented a "hold" function for radio-controlled helicopters. The idea was to flip a switch and be able to let the helicopter fly itself while you worked a camera on board. This was before drones/etc were "a thing". 3: I wrote my own version of an aerobatic team tool ("Phantom Control") for FC3 SFM after the Berkuts' legacy Phantom no longer worked / no longer supported. 4: I've written a simple autopilot that will read data from a text file and fly the viper (or any plane, with some tweaks I'm sure) around a "flight plan" similar to what I would do in the real world with an autopilot coupled to a GPS navigator. Headings, alittude, airspeed etc. 5: I've written code that "linearizes" the ED Viper throttle so that it's a flat response across the range rather than being aggressive at low % and less responsive at higher end. Again - not a flex, just commenting on my background. Now... What happens with joystick input is this. 1: Your device (FSSB, Warthog, t16000, Virpil, whatever) reads the stick position and assigns it X and Y values. Let's say it's a 16-bit device. The device will then be reporting each axis to Windows as an integer in the range of -32767 to +32767. 2: DCS scales those numbers to floating points ranging from -1.0 to +1.0. 3: DCS process accordingly. The only way DCS knows your device is an FSSB is from the text identifier it picks up from DirectInput. If in fact your FSSB is doing "something different" from any other stick and "dialing out" this left rolling tendency, then one has to consider it will vary based on airspeed, jet weight, symmetry of loading, etc. DCS would have to send that data to the FSSB and the FSSB would have to process your inputs and "do things" based on DCS data before sending its pitch/roll inputs in to Windows. I can state with an _extremely_ high level of confidence that this is not occurring. Could I be wrong? Sure. But I'd bet BIG money against it, if I were a gambler. I would be shocked beyond words if anything like that were happening. Edit: Went into the software to look. RCA turns down roll authority (saturation) when pitch is put in. Absolutely not the issue here. Jet rolls without any roll input. So as I said - I have an FSSB R3L and would be glad/curious to try whatever settings you're using. I will note that I believe Panic's video is exaggerated due to the fact that with the keyboard input, it's essentially trying to command ~ 4G even though over the top there's not enough smash, thus it's "stalling" a bit. I will agree with ED in that there are portions of the flight regime where the F-16 should have some undesired/unintended roll occurring. Whether it's inertial (asymmetric weight), reaction (to the turning of the engine) or precession (gyroscopic) I don't know. I do know the F-16 FLCS won't "auto trim" in roll like it does in pitch (attempting to maintain +1.0G unless input to the contrary). Also, many jets are "bent" a little bit requiring a unique roll/yaw trim for every jet and as with any sort of trim, you can only trim for one airspeed at a time. So...yeah. Let's see what you've got!

Short answer: - leave the TPR out of TARGET. Long answer. TARGET combines all the things it's managing into a single "controller" as far as Windows is concerned - the Thrustmaster Combined device. AFAIK, DCS still uses the "DirectInput" API for processing controller inputs. DirectInput can handle a maximum of 8 axes per controller. By adding 3 axes from the TPR, you're presenting a total of 10. No can do. Sorry.

Not without having and digging into your files. Those should've done the trick.

That was going to be my next suggestion (removing the entry from the .tmh) Enjoy! T

Not DCS or TARGET - it's a Windows / DirectX / DirectInput limit - 8 axis, 32 buttons (DX buttons) per controller. You can try this instead of your exclude... Configure(&TFRPHARudder, MODE_EXCLUDED);

So far as I know were still limited to 8 axis per controller. A full set of warthog and pedals accounts for 10. You probably don’t need to manage pedals through target but if you actually do...or want to... you have to sacrifice 2 other axes to use rudder and brakes. I’m running a profile right now that sacrifices the microstick on the throttle. Do you want to do that? First comment out these 2 lines as shown (assuming they're in your standard / default script to start with) //MapAxis(&Throttle, SCX, DX_XROT_AXIS, AXIS_NORMAL, MAP_ABSOLUTE); //SetSCurve(&Throttle, SCX, 0, 0, 0, 0, 0); //MapAxis(&Throttle, SCY, DX_YROT_AXIS, AXIS_NORMAL, MAP_ABSOLUTE); //SetSCurve(&Throttle, SCY, 0, 0, 0, 0, 0); Then you can add in the rudder & brakes like this: MapAxis(&TFRPHARudder, TFRPHA_RUDDER, DX_Z_AXIS, AXIS_NORMAL, MAP_ABSOLUTE); SetSCurve(&TFRPHARudder, TFRPHA_RUDDER, 0, 0, 0, 0, 0); MapAxis(&TFRPHARudder, TFRPHA_RIGHT, DX_XROT_AXIS, AXIS_NORMAL, MAP_ABSOLUTE); SetSCurve(&TFRPHARudder, TFRPHA_RIGHT, 0, 0, 0, 0, 0); MapAxis(&TFRPHARudder, TFRPHA_LEFT, DX_YROT_AXIS, AXIS_NORMAL, MAP_ABSOLUTE); SetSCurve(&TFRPHARudder, TFRPHA_LEFT, 0, 0, 0, 0, 0); Note, my system uses RZ and Throttle for the throttles. You could substitute DX_THROTTLE_AXIS in for "DX_Z_AXIS" on the TFRPHA_RUDDER mapping.

Thanks for the updates, folks! I'm not playing much multiplayer other than DCS these days, and I too have been using scroll lock for my PTT as long as I can remember. T

Latest Open Beta (updated 6-Sep. Hit scroll lock while in 3D world or generally during loading screens and the VR headset (Rift, at least) goes black...then returns to the default oculus world leaving your DCS completely useless until you end task on it.

Still around, still mostly fly MP...primarily formation. Still tend to see a lot of netcode twitching on everyone but the host. As in if host is flying lead, and I'm flying outer left wing, the jet in between the leader and myself is stuttering up and down. Not nearly as bad as it was a year or two ago, but still there. Teej

For what it's worth, I developed this solution because I have the ESX server running anyway for several other purposes. When I wanted to run a server in the past, I've been using my old gaming rig. That thing runs 130-140 watts the majority of the time even if it's not running the game. The current additional load on my ESX box is only about 16 watts, and I may be able to get that down even lower....plus the heat it does generate isn't in my man cave.

Well, I've solved MY issue, but it's not going to be an answer for those looking to rent a VPS somewhere, in most cases. I did in fact drop a lower end video card (radeon 6500) in my ESX server and set it to "pass through" to the VM I'll use as my DCS server. Tested and flown on.

I'm trying to bash through a solution for my own hardware. I've got ESX (vmware) running on a DL380 G6 (dual xeons, no onboard video) that I'm hoping to get DCS playing happy on. I'm fairly certain I'm going to have to stuff a GPU in there and set up passthrough to make it happen. Teej

Anyone gotten this to work in 2.1 / 2.2 yet? Thanks

This appears to be resolved in 2.1.1 in a couple of aircraft I've tested. Thanks! Teej

Typical boys. Tell 'em not to do something, that's all they wanna do. :D

Panther is indeed working the TM booth. In addition to VTB flying she flies a lot with the 476th A-10 group. We've had the pleasure of working with TM at several events over the years. Cheers!

The Patrouille de France demo team is winding up their first tour of the US in over 30 years, a goodwill mission celebrating the continued friendship and cooperation of our nations. Along the way, they met up with the USAF Thunderbirds for a joint flight over the skies of Nevada and California. The Virtual Thunderbirds recently had the honor of hosting the Jetesons for a similar mission. Here's a couple of screens from the flight. A good time was had by all! Many more shots on our facebook album. https://www.facebook.com/VirtualTbirds/ Thanks and warmest regards to the Jetesons! https://www.facebook.com/theJetesons/ --------

Possible resolution to the main problem in the thread.... In the Target folder, where the DeviceManagerApp is - try setting that (and each other) exe in that folder to run as administrator. One our team members has been having ridiculous issues with Target lately and that solved it completely for her. right click it, properties, compatibility, run as administrator. (That's Win7 - don't have a Win10 in front of me at the moment but I'm sure it's similar) T

No one else has noticed the ET / Flight clock reset? Look at the SU27 for example. The flight clock start/stop reset button (rshift C) now cycles through a half/full/no circle in part of the display, but with no change in function. ET clock start/stop/reset has no effect either.

Hey, Pac-Man: Nice detective work. I usually use the script version of Target (vs GUI) but I've had this happen when I do use the GUI as well. I also seem to have issues getting it to "pulse" a DX button properly through the Target GUI - best answer is not to use pulse for DX buttons. (I was fixing a profile someone else wrote). Either way, I've shot a message to TM about this issue and referenced your thread here. Dev team already responded that they'll look into it. T

Worked in 1.5.5 and 2.0.4. Had commands mapped to "iCommandClockElapsedTimeReset" and used to reset clock. No longer functions.