PiedDroit

IMO DCS is a gaming simulator, it simulates stuff for the purpose of entertainment (gaming). Some get offended because people call DCS a game, I think they just want to make the distinction between arcade gaming and simulation gaming. I can tell you that professional pilots don't smile after crashing in a full flight sim, it's not a game for them...

This reminds of the picture posted here: http://forums.eagle.ru/showthread.php?t=140124

You might consider contacting the server's admin and/or check with the other players if they have the same issue. I assume you have the issue only on this specific server? Also, are you using multiple screens? It's possible that only people using special resolutions are affected.

Shaw's book, I have it too (real book) super good :D I also recommend: - "No Guts No Glory" Major Frederick C. Blesse - "?" John Boyd (I don't remember which book, any reading from him should be worth it) - "In Pursuit" JOHAN KYLANDER (edit: this one is specifically aimed at rookie online pilots) Other books can be found (just look at the amazon page from "In Pursuit").

Good guess, I currently fly the ground attack derivative of the 747. Passengers are squeezed into a cylinder or strapped under the wing and directly shot to their destination for an explosion of joy when they reach it. It's called the Magnum 747. now I'm waiting for the single engine, delta wing derivative.

Glad it worked, although I couldn't tell why :huh:

Please stop the derailing, it was funny on the first time only :p

Sorry to read that, this would have been a simple fix... Is your stick behaving correctly when you're tuning the axis with the applet (where you can see the stick output)? In DCS and also in Windows control panel ? I don't have much clue... One thing you can check is bringing up the input view in the sim to see if there is actual input. Also try unplugging the stick and see if the problem is still there.

I think it's a .lua file inside the mission's file (Config/View/server.lua). When this file does not exist the client can use his own server.lua but when file resides inside the mission file (.miz), the client will use the mission's server.lua file. This has to be fixed on the sever side, the mission has to be unzipped, the server.lua file removed and zipped back. (except if they changed this behaviour in 1.5/2.0...)

Your axis is mapped on another controller besides the stick, you just need to go to controls and clean up the axis section. DCS maps all axis to all controllers by default, this behaviour is likely to happen when you plug a new controller in your PC.

Audio is cool, but it look like you used the wrong filter for the gun cam. [ame] [/ame] More washed out, less lines and less distortion.

Really? I'd be interested to see how you do it, I quite seldom go into pure vertical with the MiG-21 as I bleed speed too rapidly when doing so, and the engine is too weak to push it. Maybe you're using the emergency afterburner? I admit I never use it...

Is the intercept speed equal to max speed? I would have guessed it was lower than max speed (due to the high fuel consumption).

Also in the campaigns there are places you are just not supposed to go to... That said I would be interested if someone could post a track where he's handling this hardest A-A mission ;)

Ha fun to watch. No need to use all 3 cartridges from the beginning, one by one is enough (better keep them when your gun jams) :)

All same here, no deactivation, no issue. I'm using Saitek pedals, HOTAS Warthog and TrackIR 5, everything worked. I had this Saitek unplugging issue from time to time with Win7, but after updating to Win10 it now happens 100% of the time, I just can't unplug the pedals while the PC is powered anymore, must shutdown first :cry:

Ok, ok, back on F-117. As some said already, this aircraft is a legend and certainly deserves a place in DCS. I would certainly buy it at least to be able to fly one of those night bombing missions, but that would not happen too often, I guess. I just don't know if the current radar threat model is complex enough to replicate the challenges of slipping unseen through a SAM network. With this aircraft we could make some awesome hide and seek missions - one player takes the F-117, take off location and target are randomly selected (by mission design). Other players must intercept it before it makes it to the target :D

Well... People didn't buy it, so... :music_whistling:

I don't have the reference at hand but I recall that during the battle of Britain spit pilot would take very limited amount of fuel to get max performance againt the 109s. I guess that doesn't cover your time frame but still a good example.

Good idea. A possible implementation would be a map viewport showing the F10 map (kind of "minimap"). That could be disabled in mission options.

I'll check that this week end (device analyser). I forgot about this feature, good find. The sensor itself is very accurate but due to stiction you might not have a smooth motion in some places. If that's a big problem to you, you can disassemble it an polish the internal moving parts - not easy to do.

To answer your questions: empirical. If your device has calibration issues and/or jittering in center (or left or right) then you'd use deadzones. Yes, S curve only defines the shape. I suggest you take a look at the target script manual for the définition of all parameters. There are also other types of curves (J curves). Glad it worked, 10 might be a bit too steep - the scale is not the same as in DCS :) Cheers

That's an example from the manual ;), in your script only change the second to last parameter (others be 0), like this: MapAxis(&Joystick, JOYX, DX_X_AXIS, AXIS_NORMAL, MAP_ABSOLUTE); SetSCurve(&Joystick, JOYX, 0, 0, 0, 4, 0); MapAxis(&Joystick, JOYY, DX_Y_AXIS, AXIS_NORMAL, MAP_ABSOLUTE); SetSCurve(&Joystick, JOYY, 0, 0, 0, 4, 0); Unfortunately there is no way to see what the curve looks like graphically (well, I suppose using the correct formula we could plot it on graph viewer like the ones on scientific calculators but I don't have the formula right now). EDIT: You should use the DCS axis tuner to tune your axis (no TARGET), I think it will be easier for you (and more visual too), unless there is a specific reason for this (other sim that don't have axis tuning). EDIT2: Also, using TARGET will create a new, different controller (Thrustmaster Combined), if you already change the buttons assignments you'll have to do it again for this new controller. I definitely recommend to tune the axis inside DCS! I personally use TARGET for some special functions (teamspeak, trackIR, remapping), but everything else I do in DCS, it's much easier to tune ;)

Just take the one above (in my first post in this thread), change the curve using the second-to-last parameter of SetSCurve calls (I suggest starting with a value of 3 or 4). Here's an extract of the manual (page 28 of the pdf):

Yes but only for the stick. If you use TARGET for both throttle and stick, all buttons on the stick will have correct DX assignment by default but throttle buttons will only get remainining free dx assignments. Dunno if I'm clear... It's a bit confusing. Right now I'm using the phone to answer it's not very practical. I'll make a more detailed post later. EDIT: So, when TARGET is started, it will create a controller that has DX1-32 buttons and axis assigned by default. Stick DX1-19 and DXHat buttons will be mapped to DX1-19 and DXHat Throttle D1-32 will be mapped to DX19-32 (some buttons won't have a DX buttons assigned). Axis will be mapped like this: Stick JOYX (DX_X_AXIS) -> Combined (DX_X_AXIS) Stick JOYX (DX_Y_AXIS) -> Combined (DX_Y_AXIS) Throttle SCX (DX_X_AXIS) -> Combined (DX_XROT_AXIS) Throttle SCY (DX_Y_AXIS) -> Combined (DX_YROT_AXIS) Throttle THR_RIGHT(DX_Z_AXIS) -> Combined (DX_Z_AXIS) Throttle THR_LEFT(DX_ROTZ_AXIS) -> Combined (DX_ZROT_AXIS) Throttle THR_FC (DX_THROTTLE_AXIS) -> Combined (DX_SLIDER_AXIS) If you want to use a customized Throttle that runs with TARGET and seen like a non-TARGET throttle (will all DX buttons corresponding to the non-TARGET throttle), see this post. Finally, you can setup TARGET code that will run separately from your HOTAS, useful to generate keystrokes while using the HOTAS as if it was not controlled by TARGET (in that case there will be no Thrustmaster Combined and you won't be able to change any axis or DX assignment). To do that, use the setup as in this post.