SmokeyTheLung

Unfortunately I'm not enough of an expert to give you a proper tutorial. But I will suggest that you acquaint yourself with the TrackIR software and start creating a custom profile. It sounds like increasing the sensitivity on both the X and Y axes will solve issues 2 and 3. Issue number 1 might simply take some getting used to.

I hope you guys might consider running the air to ground server with both fighters and strikers (the way it's been since FC3 came out). I can totally understand wanting a full air to air "furball" server but I think what made your server stand out for the DCS crowd (a10/ka-50) was the added threat/excitement that fighters brought to the action. One of my most exciting moments since I started flying simulators was shooting down a Mig-29 in an A10C on your server! Hope I get to try that again (and probably fail :D)

IIRC laser guided bombs have two selectable trajectories, ballistic and optimal. Optimal is the default setting (can be changed in the DSMS). Optimal actually attempts to put the bomb ahead of your Intended target. I think the idea is to have the bomb falling as vertically as possible during terminal guidance so as to have enough energy to manuver accurately. It's possible that this accounts for your bombs hitting/not hitting the moving vehicles depending on the direction you are dropping relative to their movement. I've had the best results with laser guided bombs by guesstimating a bit of lead on the moving targets. Lasing too early shouldn't be a problem, as the bomb won't "see" the laser (and start maneuvering/losing energy) until its fairly close to the ground. Try dropping a bomb, switching on the laser immediately, then press F6 and watch the bomb fall. Try to take note as the when the bomb starts guiding to the laser.

A video you've probably seen of an A-10A pilot engaging armor in Bagdad, 2003 I think. It's pretty difficult to read the HUD, but he's definitely engaging very close.

As close as they can, while still being able to safely recover the jet.

The MFCDs have rocker switches that control brightness and contrast (not the same as gain/level for the FLIR) at the corners of the display. Switching an MFCD to night mode just changes the default levels. You can change them to the default day settings for the TGP only if you like, I think that should solve your issue. Note that the settings that you enter are only for the current page that you have displayed on the MFCD.

Did you use the prepare mission function? Once you do, the DSMS will be "locked" so to speak. AFAIK the only way to fix the issue is to unzip the mission and edit some code (unfortunately I'm not sure what to edit)

Bump :) Both issues are still present in 1.2.3. Also, a quick question for the experts: HUD SPI submode while using one of the consent to release options has the SPI collocated with the "actual" CCIP solution instead of the pipper in its pre-designate/out of solution state. Is that correct?

In the photos you linked you're zoomed in with the co-axial machine gun selected. If you switch to the main gun and zoom in you'll see a more authentic looking reticle

On the waypoint page there is a an OSB to the right of a number, followed by a question mark (for example: 7?) The number represents the next available waypoint that you can create. Did you press that OSB?

In many A10 HUD photos/videos you can see what appears to be a reflection from the cathode ray tube (? I think that's what the a10 HUD uses). It only appears in certain lighting conditions and takes the form of a green circle superimposed over the normal HUD symbology. Is that what you're trying to simulate, or just an overall combiner glass tint?

Look here to start: DCS World/Mods/aircraft/Ka-50/Cockpit/Scripts/config.lua ...I got this working a few days ago, but I can't remember the exact path and I'm away from the home computer

A truly outstanding improvement! Thanks!

Cool interview Wags, nice to hear a bit of your story and get updated on the roadmap. Thanks!

IIRC china hat forward long slaves all sensors to the SPI, including the TAD cursor. So if your SPI is set to a waypoint that is not visible for the given TAD scale, it'll zoom out to a scale where the SPI is visible. China hat aft long slaves the TGP (and only the TGP iirc) to the steerpoint. Maybe that accounts for what you're seeing?

Sounds like you need to up the engine RPM. Next to the throttle there is another large lever for engine RPM, I think it's clickable...if not it should be in the controls as "engine RPM"

If you move your eye point in the cockpit back a little bit this is minimized (at the expense of HUD readability). You can do this by editing files (I think) or by using trackIR. I use the trackIR method occasionally. The trick is to get comfortable in your chair, than lean forward a few inches, center your trackIR, than lean back and get comfortable. If you use trackIR this might be a nice quick fix. If not, it's probably not worth the hassle as the HUD readability is quite limited with a fixed centered view and the eye point moved back.

Damn that looks good

Was it the SA-8 OSA (Gecko) that shot at you? That uses command guidance, and flares won't do the trick. Chaff and Jammer might help

I don't know much about the real superbugs avionics, but the simulation created by VRS is certainly very believable...definitely as complex/in depth as DCS products (it may not be as accurate as DCS though, we'll have to let the F-18 experts weigh in) My opinion is that the cockpit shape looks a little off (pure conjecture, as I've never sat in the real deal). The canopy bow is especially jarring for me, looks a bit like an old school 2D pit in that regard. The flight model feels okay, but I've heard a few grumbles on that front. All in all a very cool product. Also, I'd be happy to send along my WIP target profile. It would seem that the person(s) responsible for the HOTAS ergonomics on the A10C were not involved in the Superbug development (it's subtle, but some of the common buttons/concepts are mapped in a different way) I've attempted to create a profile that's a little more in line with the A10s design, which is thoroughly ingrained in my mind at this point.

You have to use target.

I'm a new FSX/Tacpack user, so there's probably a lot that I don't know how to do yet... Basically what you listed is what's immediately available for a vanilla FSX install with tacpack; You can spawn drones and sam sites while flying and of course you can blow up static targets and FSX air traffic. AFAIK moving targets are a feature of FSX@War, which I don't have installed. My first impression is that it is indeed very limited (not just MP). However, I've been having a blast getting used to the ergonomics of the Superbugs avionics. A2G RADAR! :pilotfly: HARMS! Awesome!

I've got to give this thing a decent review. I'm not exactly in love with the flight model or cockpit. Most of the cockpit is great, but the size and placement of the canopy bow is a little jarring (ED set the bar for me :pilotfly:). Avionics wise, it's pretty believable and definitely an all around cool jet to fly. Too bad it's FSX and not DCS.

Thanks a bunch, great initiative

Now that's a good point :D