PiedDroit

True... but kingfish is right, the weapon system sees this as a single missile that is shot twice.

this topic has already been discussed, this is not the place to revive it. The object visibily feature is needed and many people have asked for it (including me). The topic raised is that people not willing to use it (like you I suppose since you dont seem to deem it necessary) might consider themselves at a disadvantage.

Hello, this is a very interesting debate, as some options can be considered cheats when they are mean to even the game. For example, removing the grass in arma 3 could be considered unfair to other players because of the edge it gives, when this is mean for smaller configs to make the game playable. The enlarged setting could be considered mandatory for Oculus users because they don't have the finer resolution that a monitor has. In the old days (when every pixel counted lol), when everyone were limited to 800x600 (or worse), having one of the new, expensive 1024x768 or higher monitors was sometimes considered a "cheat" as it was giving an edge to those people. IMO, stuff like automatic start, enlarged settings etc, should not be locked and categorized as hard cheats, instead they should stay open to everyone to use (except on ultra-competitive server maybe but I don't even know if they exist). It may, or may not give some edge over those who don't use it. I like the fact that the automatic start is available to anyone, as it allows people that don't want to go through the complex startup procedures to enjoy flyin gwith anyone else.

Yes! Bring it!

Hi, I tested that today, I confirm it works :thumbup: This opens a new world of scripting possibilities!

Super news! :thumbup:

Oh that's sneaky :D I'll keep you posted when I have tried it, no time today.

A-7, yes. I didn't see the other two, but I admit I'm not following their pages too closely :music_whistling:

Hi, you should contact the manufacturer as you shouldn't have that many issues. You could expect some little issues but nothing that big. To give you an idea, mine is 3 years old, I only disassembled it to polish the "ball" and put some brand new grease. I also added a little plastic tab on the right throttle because it was too wobly to my taste but nothing dramatic. All switches are working perfectly, some are a bit loose but they work fine and they don't deteriorate over time so it seem normal.

I have other attack aircraft before this one in my "wishlist", namely Super-Entendard, A-7 and A-6. But, why not.

Hi, I tried your method but it makes the joystick and throttle disappear completely from the windows controller list and the thrustmaster combined is not created either. This way you can only emulate keystrokes, the axis are not seen at all. What is the supposed effect of this code? The code I posted above will keep the joystick and the throttle visible to DCS while allowing the user to customize the throttle output at the same time, with minimal change of configuration. So, is there anything to add to achieve the same with the Init() modification? Maybe there's another code modification I don't have. Thanks!

I think the TrackIR Z axis is bound to zoom by default, hence his problem.

You can find videos of F/A-18, F-15 and F-16 popping chaffs, I suppose the russians are also carrying them on a regular basis.

I don't know if they carry it but they exist for sure: http://www.ordtec.com/FlaresIR.html Search "OMI-CHF-26"

Cool this looks like much simpler than my solution, good find :thumbup: I'm gonna try that some day

Actually you can create a TARGET profile for throttle only that will look like the throttle (without TARGET) from a DirectX point of view. This will allow you to customize the throttle via TARGET on top of the default profile. -1- Get file _DefaultMap.tmh, this file contains a button mapping (ThrottleMap1) that will restore all default buttons for the throttle (i.e directX mapping). You can't use it with the throttle+joystick because the directX mappings of the joystick and throttle will overlap. The .tmc file is attached, this is the command that load the new mapping: MapList(&Throttle,&ThrottleMap1); // _DefaultMap.tmh -2- Copy the content of \DCS World\Mods\aircraft\A-10C\Input\A-10C\joystick\Throttle - HOTAS Warthog.lua Inside file \DCS World\Mods\aircraft\A-10C\Input\A-10C\joystick\Thrustmaster Combined.lua (make a backup for it first). Also backup (and delete) file \Saved Games\DCS\Config\Input\A-10C\joystick\Thrustmaster Combined {7B669F90-9A15-11e2-8002-444553540000}.diff.lua --- You can test the .tmc file alone and check (with windows controller test tool) that the throttle and the throttle+TARGET have the same DirectX output. Step 2 ensures that the combined and the throttle will behave the same in DCS, you can test it, start the profile in TARGET, start DCS and check that the throttle switches and axis work correctly. At this point you can add your custom stuff in the TARGET script. --- EDIT: You can do the same for the joystick except you shouldn't have to redefine anything, an empty profile will do as the default mappings in TARGET are those of the naked joystick. If you want to customize for throttle and joystick at the same time, I'm afraid that won't be possible, you'll need to rebuild a full TARGET profile that remaps every keyboard command to the HOTAS buttons before anything else. _DefaultMap.tmh.txt ThrottleOnly.tmc.txt

The cursor in DCS has fixed distance and doesn't change size. Depending on the distance eye-panel, the cursor can be floating in the air in front of the panels, or appear to be behind the panels (but still visible), which makes aiming it very akward. The P3D cursor is "following" the panels surface and changing size according to the distance which makes aiming it super natural.

Good luck with the new aircraft, you don't owe anything to anyone so it's perfectly OK to switch to another one that will be easier for you to do.

Did you try creating your waypoints with minimum altitude ? The default alt is 2000m for a newly created waypoint, then you can change the value, it will default itself to ground level if your input is lower than ground level. This way you won't have to edit your flight plan fromthe cockpit.

Actually it can, it's the 3 camera lua config file, it configures 3 viewports, one in front and one on either side. having those on the side add to the speed impression as you see the scenery traversing in your peripheral vision.

I have 2xASO-2, 4xR-60, 2xR-3R APU13MI, and fuel 490L too. My stock patrol medium range also uses 4xR-60.

the cartridges were only needed in case of misfire (and to arm the gun the first time). the gsh-23 only has 3 of them. Edit: the gsh-6-30 had 10, I saw nothing stating that they were needed for every burst on this particular gun, that'd be an interesting thing to know if it was the case.

First of all check in-game, without trackIR, that you can actually see your 6 o'clock, some view settings may prevent you to do so (use num keys to look around). If you can check 6 without trackir, you may start TrackIR but not DCS. With your hat clip on, move your head around and check the camera output when your in-game head reaches 6 o'clock position (you can see the Raw/Game values in the trackir window as well as what the camera sees). What can happen is: 1. the ratio (rotation speed) is too low and you end up masking one of the three reflectors by turning your head too much. -> adjust rotation speed. 2. one reflector is going outside the camera FOV. -> change camera position 3. something else is seen by the camera and perturbates the tracking (glasses, sun reflection that becomes visible). -> adjust camera sensitivity -> dim or move external lights if possible

Interesting shape

Yes it is more accurate - and it works better with some angle. If your attack run is made with too shallow angle your piper might become jumpy as it alternates between two firing solution.