LawnDart

Great as always! Amazed by the ingenuity and showmanship.

Good catch! Copy and paste got the best of me... :doh: Fixed.

What's the difference between Bunker 1 and Bunker 2 in the spreadsheet above?

SimHQ: History of the Fairchild-Republic A-10 Thunderbolt II, Part One, Part Two Excerpt from the article above: Not sure how accurate those numbers are (!), but it gives you something to go on unless you can find another source for the A-10's (sustained) roll rate. Using this information while performing three consecutive aileron rolls: SPD BRK 40%: (360 x 3) / 200 = 5.4 seconds SPD BRK CLSD: (360 x 3) / 130 = 8.3 seconds What roll rate does the sime give you at 300 knots?

Unless it is a replica, it wouldn't satisfy... :smilewink: You ever consider the other way around... It would let you use the new handle on the Cougar base if you'd like. That's great for all those (F-16) pit builders! (The new handle has realistic pressure on buttons and switches etc.).

I found a "bug" with the F-16 FM. The "bug" is that the F-16 FM's HUD doesn't switch to barometric ALT until 5,000ft MSL, which means between 1,000ft RAD ALT and reaching 5,000ft BARO ALT you have no altimeter readout on the HUD tape whatsoever*! The only way to tell your altitude is by the steam gauge on the center pedestal. (The F-15 FM's HUD still works exactly as it did in FC1 with one RAD ALT scale below 1,000ft AGL and another RAD ALT scale between 1,000-2,500ft AGL before switching completely to BARO readout above 2,500 AGL). *The exception with the F-16 FM is if you're banked more than ~60 degrees and or a steep enough climb/descent angle for the RAD ALT to function, then the HUD switches to BARO readout. However, as soon as you're within those angle limits again, anytime below 5,000ft AGL you lose the altitude tape on the HUD since it's scale immediately goes to 1,000ft and below (even if you're at an altitude between 1,000-5,000ft AGL). Has anyone else noticed this with other planes using "HumanCockpit" (and a borrowed HUD)?

What does efA stand for?

Spring starts at the vernal equinox (21 March) and ends at the summer solstice (21 June).

I've added a few airplanes as "HumanCockpit" and can't seem to get the snapviews to work for them. Has anyone added tweaked snapviews for aircraft made "flyable" in FC2 (e.g. F-16, F/A-18, Harrier, Tornado etc.)? I have the F-16C-2 added as plane index = 10 in the view.lua and server.lua... but when adding a [10] to the snapview.lua file it doesn't seem to recognize it. The snapview.lua values for plane [8] (which corresponds to the F-15) work fine to change the default angles for the F-15 only, but when the same cockpit is used for another "flyable" (such as the F-16) those values don't seem to apply anymore even if the F-15 cockpit is used. Adding the index number in the snapview.lua for a new plane (e.g. [10] as mentioned above) doesn't seem to work either... What am I missing here...? So, basically: How can you change the view angles in the SnapView.lua for added flyables?

SE, I see the cat's out of the bag now... ;)

Thanks! I knew it was somewhere, just didn't know where to look for it... :)

Seems the values in the SnapView.lua don't make any difference in FC2? Been trying to change the F-15's default cockpit angles, but the values I enter make no difference. Is there a new place where these are saved in FC2 or am I missing something? I'm trying to change the value in red to a positive number ( = 5), but in game the view still defaults to its old position (= -9.6784505844116). :huh: Snap[8][13] = {} Snap[8][13]["y_trans"] = 0 Snap[8][13]["x_trans"] = 0 Snap[8][13]["hAngle"] = 0 Snap[8][13]["viewAngle"] = 88.727844238281 Snap[8][13]["vAngle"] = [color=red]-9.6784505844116[/color] Snap[8][13]["rollAngle"] = 0 Snap[8][13]["z_trans"] = 0

I somehow missed this topic at first, but that quote made me laugh a little!:megalol: The VBA did just fine in 1.12 with 6 jets, so I don't think they'll downgrade to 4 jets in FC2. :smilewink: Nice screen setup though.

Backup your original file and consider the caution observed! Have fun testing! :)

This has already been answered (sort of), but I hope the LAT/LONG-, and distance tool- fixes are also scheduled for DCS: A-10C.

I can see how modded FM's would impact the game negatively if allowed in combat... that said, SE, if you find where to tweak "auto trim" would you mind sharing it (hate flying the Viper having to trim it = unrealistic. Supposed to be point and forget ;) ).

Has anyone figured out if there's a way to use "auto trim" (like the F-15 has) with the other flyables?

I used to have a Dlink "gaming router" and would constantly lag out. It's still the most laggy router I've ever used. Got rid of it and bought a vanilla Linksys - everything works. Bow, also see what happens without your router (if DMZ doesn't change anything), routers do go bad ocassionally...

Thanks SE, I found the answer to this almost immediately after posting my question. That's great. Basically means the modding potential is endless, since it uses its own set of 'rules'. :thumbup:

To simulate reality. Your helmet, ejection seat and harness would be in the way IRL and preventing you, unless you have no ligaments in your neck. :smilewink:

Bow, add a DMZ on your router for the local IP in use and see if you get the time out still? This way we can at least isolate the problem to the router OR something else.

Very nice video Ange! Inspirational...

Which axis assignmets (curves) are applied to the (AI) planes you make flyable? (Reason I ask is because FC2 has different settings for the A-10A, F-15C, SU-27 etc. whereas FC1 had a single universal axis setup for all planes).

Looking good "Airwolf"! (Reminds me of the flag panel on Thunderbird aircraft).

Thankfully FC2 supports WS so this issue is gone (should you get a copy).