PiedDroit

In that case, simply ask for a feature to work, period ;) You can't say something like "this feature works in sim X, make it work in DCS", it doesn't make sense. Of course a broken feature should be fixed, but how does it relate to the other sim, are they sharing the same engine?

There should be improvements in 1.5 ("fixed tracks" in changelog). And BTW, you can't compare two sims - it's irrelevant, as one would say ;) You can ask for bug fix (which is in 1.5) and features (wishlist), but who cares if it works well in another sim? Different, code, different engine, etc :p

Super video, I's really cool to have such updates, thanks! :thumbup: If we compare it with real videos it behaves like it should, maybe a little less smooth (esp. radar piper) but it's hard to judge yet. What's interesting to note is that this sight is of the "historical" type, i.e. it will plot the path of the bullets if you would have fired continuously. So the prediction is good when stabilized for a second of two. On the joke side, I was thinking, this reminds me of a certain game I had on my Nokia 3310 :D

You can put your target on the side of the nose, on the side you plan to roll (eg. 11 o'clock if you plan to roll left), this will help you to keep sight on the target while climbing and rolling. With practice you'll do it eventually ;)

Hello, you can use TrimDXAxis. There you go, here I mapped Joystick X axis to both X and Y, note that 2048 is the maximum resolution you can using this method: KeyAxis(&Joystick,JOYX,0,AXMAP1(2048, EXEC([color=DarkRed]"TrimDXAxis(DX_X_AXIS, SET(Joystick[JOYX]/32)); TrimDXAxis(DX_Y_AXIS, SET(Joystick[JOYX]/32));"[/color]), EXEC([color=DarkRed]"TrimDXAxis(DX_X_AXIS, SET(Joystick[JOYX]/32)); TrimDXAxis(DX_Y_AXIS, SET(Joystick[JOYX]/32));"[/color])));Edit: Joystick[JOYX]/32 is used to make resolution of the axis (65536) match the resolution of the trim (2048=65536/32). Read page 30 of the pdf manual. Edit2: you can even use a third controller axis that will be mapped to two other directx axis, here moving the slider on the throttle will set both joystick X and Y, with less steps (512 instead of 2048 ): [color=#a52a2a][color=Black]KeyAxis(&Throttle,THR_FC,0,AXMAP1(512, EXEC([color=#a52a2a]"TrimDXAxis(DX_X_AXIS, SET(Throttle[THR_FC]/32)); TrimDXAxis(DX_Y_AXIS, SET(Throttle[THR_FC]/32));"[/color]), EXEC([color=#a52a2a]"TrimDXAxis(DX_X_AXIS, SET(Throttle[THR_FC]/32)); TrimDXAxis(DX_Y_AXIS, SET(Throttle[THR_FC]/32));"[/color])));[/color][/color]

Most extremely probably not. That would be equivalent to shoot a 30mm shell in one's foot.

Lol nice, thanks for sharing the solution :lol: :thumbup:

Also, disable the hotkeys for actions you don't use (uncheck "enable"), as TrackIR software will trap them, which can be problematic (F7...).

Hello, I took some time to go through the track in more details. 1 Dive angle, a little shallow but not too dramatic, I could get good precision when I tried (the jumpy piper will occur at much shallower angle, almost NOE). 2 What is really killing your aim is the wind. A short burst at a distance will tell you that your shells are pushed a lot to the right. In that case it's better to do another attack from a different angle (try 90° first if you don't know the wind direction then make corrections, with rain it's easier to estimate it). If you still want to make the shot, then proceed by short bursts until you get the correction right, but in that case it will be difficult to put a decent amount of ammo on target (in that case you have no choice but to use the rudder to adjust the aim...). 3 I took control and tested it myself for about 20 minutes, while I could take out the first target on first or second pass, no matter how much hits I could put on other targets they weren't destroyed. The pods are useful on very lightly armoured target, for anything equal or bigger than an APC it's better to switch to main gun or go back and rearm. It's still possible to take out APCs with the pods, it requires concentrated fire which puts you at risk of return fire since you need to be very close. Pods are better used as area weapons from a distance. Also, I remove the burst limiter (LShift+C), personal preference (otherwise each burst is limited to 25 rounds IIRC). Hope this helps ;) I can post a track later if it might help, using your same setup.

There's some cool stuff the commercial aviation has and we don't (yet), like FLIR view projected on the HUD, that's really neat:pilotfly: Regarding the 2000, I don't know what will be used for precision navigation, INS and ILS? I don't remember if there's a GPS or not

Maybe it's displayed only when the desire accuracy is available. Even with synthetic runway display you wouldn't land in low visibility without cat III approach anyway

Yeah altitude, attitude, very similar names, totally different purpose :D

It doesn't keep altitude! You use it to make a steady climb or descent. or just to keep the plane flying straight where you are pointing. Edit: in the A-10C this is the "PATH" mode.

This is indeed a big cause of jumpy piper ;) The computer has troubles finding the good impact point and alternates between two solutions, a deeper dive will solve it.

Oh I smell revenge, were you killed once by this one extra round? :megalol:

Here's my own fuel dump method: If your AB is still operating you can turn around base with full AB, this will burn fuel quickly (with added fun of going super fast). This doesn't work well for emergency obviously ;)

Ahh punk :D, listened a lot of that long, ago, still listen occasionally, still love it ^^ Here are a couple of songs from a spanish rock/punk group, Extremoduro: Pepe Botika (¿Dónde están mis amigos?) A Fuego And another, french group, Ludwig von 88: F*stf*ckplaya (sorry can't write the song title here) New Orleans: Discover and enjoy

That is NOT the correct to handle view ports. The correct way is to create the appropriate viewport in the monitor .lua. In that case, try creating a viewport named "KNEEBOARD" and put the new coordinates there

So, discussing anything that is not 100% realistic is worthless? Haha funny. Anyway, I remember a statement about dropping the A/G CCIP completely but I just don't know what's the plan... If this capability will remain, then it should be debugged (I personaly don't mind having it, it's better than nothing and I probably won't drop any bomb using the charts anyway).

If you use it at the very end I guess it's okay (for a snapshot or to spray on a wider surface). In crosswinds I don't remember how I do it... I suppose I would approach normally (i.e keeping the ball centered, with target slightly off the piper) and use it only at the end of the attack, to put the piper on target. I need to check what is actually happening though. Bottom line is, try to do a good approach without slipping.

For better answers, attach a track :thumbup:

Don't use rudder! It will throw your aim away quickly. If you need to do lateral corrections, bank the aircraft slightly, or abort and retry. Try approach from far away first (heading directly on target), then try putting target at 10 or 2 o'clock and rolling on target closer and closer. This way you'll become better at doing a good, steady approach. Practice ;)

there's definitely something with 1.5, I remember trying stereo. lua (no DK2, but on 1.2 it shows 2 views) and it didn't work either (same "squeezed" view as you described).

Same here, I'm using TARGET with only keyboard mappings, no issues at all. (Gear, flaps, IR/SAR switches are mapped on it).

As said, may not work on 1.5. For 1.2, here's one file that will work: 1Camera-GUIcenter.lua: _ = function(p) return p; end; name = _('1 Screen - GUI centered'); Description = 'One monitor configuration' Viewports = { Center = { x = 0; y = 0; width = screen.width; height = screen.height; viewDx = 0; viewDy = 0; aspect = screen.aspect; } } GUI = { x = screen.width/3; y = 0; width = screen.width/3; height = screen.height; } UIMainView = GUI You can try with hardcoded values if you like: 1Camera-GUIcenter.lua: _ = function(p) return p; end; name = _('1 Screen - GUI centered'); Description = 'One monitor configuration' Viewports = { Center = { x = 0; y = 0; width = 1920*3; height = 1080; viewDx = 0; viewDy = 0; aspect = 1920*3/1080; } } GUI = { x = 1920; y = 0; width = 1920; height = 1080; } UIMainView = GUIMake sure you select resolution 5760x1080 with aspect=5.3333333 in options. This always worked in 1.2, if you still have troubles with it I don't know what could be the problem, then go for the radio menu modifications.