Meyomyx

It might be a good idea to post a quick message on the main DCS site if this is widespread? Without any access, the only thing I could do was to submit a ticket. Oh and I changed my password as a precaution :cheer3nc:

+1

Am I the only one that thinks that the amount of pitch input needed to rotate the aircraft seems excessive? It takes a LOT of rearward stick to rotate .... which you have to release significantly once in the climb. Maybe that's accurate. ... oh before you mention it, T/O trim is always selected :thumbup:

I find slider is good as said above - and the advantage of the slider is you can set the zoom amount instantly, rather than waiting for a bound button to zoom in or out.

Coolie hat DOWN

Set each one to 20,35,63 (day or night) - then use the "DSP" rocker (top right). You can tweak the BRT from 25 down a few notches on the odd occasion. I bind "DSP" to a pair of keys for each MFCD so I can alter the brightness easily. Some maps its worth turning Auto charts to Manual - then use the "ADJ" rocker (top left) to set the chart you want. This works particularly well for the Gulf charts ...

I just discovered that the BRT DOES alter the intensity of the whole MFCD INCLUDING the TGP symbology so at least it can be made less bright. A sort of workaround

Hi Wags. No - SYM does not adjust the white symbology of the TGP screen ("Not SOI" adjusts with SYM and the other display symbology). It remains at the same intensity.

I'm trying to get a comfortable night lighting balance and there's a couple of oddities. I'm not sure if any of these are how they should be but: The TGP symbology is at a fixed brightness making it extremely bright in a dark cockpit. I would have expected it to be controlled with the symbology brightness control? Similarly, I would have expected the clock, UHF repeater and NMSP would be controlled by panel lighting somehow. Once again, with everything else dimmed, they are set at maximum brightness. The AOA indexer brightness control doesn't seem to do anything. Now, other controls on that panel are not operational at the moment, but the manual implies that this one is? Finally, I note that the HMCS day and night modes (on the profiles page) appear to be reversed - the night mode is much brighter than the day mode. I think that should be the other way around. Details, details .... :) Keep up the awesome work

If you have Warthog, use the grey "friction control" slider axis on the throttle for zoom. Its very easy to use and find and has a centre detent. Best kept off TIR in my opinion.

It's worng to move the viewpoint back - and a criticism of many sim set ups. What you're trying to do is replicate your FOCAL view, which is quite narrow. Here's the test: Assume that your monitor is roughly the distance between your eyes and the panel (that is, you can just about touch the screen with an outstretched arm). It follows that the object you touch would be 1:1 size on the screen. The UFC, for example, should be the size of the UFC on the screen. In the image above, it's about 2 inches wide on my monitor. Thus the object you're looking at is readable, as it should be, without any zooming. The HUD information will be the size it would be IRL. Remember, we're not talking about peripheral view but FOCAL view. To look at another point on the panel, you would move your head. In real life, if you were now to look at the gear handle, for example, you would move your head quite a bit to normally FOCUS on it (once again, we're not talking about your peripheral vision). To check your fuel content, you'd look down and right and be able to read it easily. In any sim, if you can see the whole panel, your view point is way too far back. In the example above, you can focus on any part of the whole panel by simply moving your eyes slightly. In reality, you'd be moving your head quite a bit. Now, of course, there must be a little compromise here (especially if you have no head tracking). BUT, the problem with assuming that the view above represents a normal focal view, is that the displays and instruments are so far away, you can barely see them. You should not have to zoom in to see information on a display that you would normally be able to read easily IRL. The final test - imagine you're sat ion the cockpit (and you don't need to be a real A10 pilot). Look at the yellow manual canopy release handles on either side of the cockpit. You'd be moving your head through about 90 degrees to look at these. In the image above, you can simply move your eyes slightly.

I just came across this interesting video that shows what I mean. The ground disturbances are noticeably reduced into the high speed phase of the ground roll

The A10 (in particular) seems to be affected by ground roll surface bumps to the same degree right to the point of lift off. Even close to Vr the effect on the aircraft is the same. The video explains - at 130kts we pass an intersection with significant bumps. During the high speed phase of the take off roll, there would be a significant amount of lift damping the input from ground bumps. The effect of bumps needs to be damped in proportion to airspeed.

I use this. Use small inputs for precision but full deflection moves at a reasonable rate

unitsystems.lua needs to have the following entry appended: ["A-10C_2"] = "us" .... or all the units are metric. Cheers :)

There is a report in about the fuel selector detents being incorrect until you move it to full travel each way, by the way

As per the attached image, the wrong Maverick type is reported and no mention of CBU load. Also, JTAC specifies "use ......." and then nothing. Presumably this indicates free weapon choice but it would be good to trap this condition.

You need a TPOD. The weapon can't establish the release parameters - it isn't clever enough. You need to use the pod, slew to the rough area and then activate LSS mode. The pod will search and find the lased point. Select that as your SPI and THEN the aircraft can calculate the release solution. I'd be surprised if an aircraft were dispatched with laser guided weapons with no means of designating targets. If there was a problem with the JTAC in any way, you'd have an aeroplane full of weapons with no means of deployment! I might be mistaken :)

Swap two functions and try it (for diagnostic purposes). Make the paddle do the MM switch (for example) and the MM button do the paddle. It sounds very much like some other application is sharing the same interrupt.

You need a search function to search the forums you want to search in!

Figured it .... Groundspeed/Airspeed and a coincidence of the difference between the two. What I can't work out is how to delete the post!

A simple mission to practice refuelling. Originally the mission had the tanker flying at 180kts - set in both waypoints and with NO orbit instruction. When the tanker speed is amended to 215 in both waypoint speeds (and saved), the tanker speed is still at 180. Even now if I open the ME, the speeds are all at 215 (or even edited to 220kts) yet the tanker clears contact (and is operating) at 15000ft at 180kts. There is no orbit instruction or wind component. FUEL.trk image_259266.miz

I've had a similar thing recently with the A/P not disengaging (Warthog). On operating the paddle switch, the double dot disappears but the altitude hold function remains active (as if only "half" working). Try unbinding "undesignate" in controls and then re-binding the paddle switch. Seemed to resolve the issue. If I end up replicating the issue, I'll grab the track.

MInor issue - selector starts out of the selection detents. Rotating fully in one direction restores detent positions. FUEL.trk

Hi! There is no FrenchpackScript.lua or Frenchpackscript01.lua in the ZIP archive. I'm presuming it's changed .... The only thing I can find is a file called ModpackScript.lua in the v3 ZIP Unsure which .lua to run Thank you!