jaylw314

I was talking about some of the hardware he's managed to find, but that too

I don't know where that guy is getting his stuff for his project, but holy cow, some of it's pretty cool!

Is anybody SURE the power switch is supposed to be a momentary two-way switch? Could it possibly be a two-position rocker switch that has not been animated yet? I don't know for sure, but it's described as a 'two position rocker switch', where the brightness and contrast switches are described as 'two-position, spring-loaded-to-center rocker switches'. That doesn't prove, but does strongly suggest the power switch is a OFF-ON switch, while the other switches are (ON)-OFF-(ON) switches, where the parentheses mean momentary or spring-centered.

I just LMAO at the title of this thread IIRC, the speed I saw for the KC-135 refueling A-10's was 220 KIAS, I think I used 18,000' MSL and 290 knots groundspeed in the Mission Editor and it worked out about right

I've seen some situations where when you jump in the WSO seat but you're still stuck with the pilot bindings until you go to Settings->Controls and change the category from F-15 to F-15 WSO. I'm not sure what those situations are, though IIRC, there are no animations for the WSO hand controllers yet

Not wading into the realistic vs unrealistic sound squabble, but for now, at least until avionics overheating is implemented, you can turn the ECS off. Alternatively, setting the AC to MIN and/or setting the ECS to left or right only allows for a couple steps to control the overall volume. AFAIK, setting AC to MIN and ECS to L/R only does not trigger the display cooling warning.

Thanks for the follow up on that!

I just gave it a try and could not reproduce this. Made TGP SOI and SPI, made a mark point with TMS right short, changed the STEER knob on the AAP to MARK, then slaved the MAV page to the TGP with China Hat forward long. Had to wait to get to about 8 nm slant range before the MAV would lock with TMS up short, then launched as usual. Aside from the possibility of some bug impossible to reproduce without the same exact set of circumstances nobody can know without a track file, some possibilities come to mind: Forgetting to set a MAV profile. This fits everything you've described and you still haven't confirmed this was done. Results in "SENSOR" on the left edge of the MAV page. Forgetting TMS up short to lock the MAV. This is not required when MAV is slewed, but required when slaved. Also could be too far away or have insufficient contrast to lock. Results in "No Track Launch Inhibit" warning Accidentally pressing TMS right long. This makes your most recent markpoint SPI, so if you had to fiddle with the TGP to get on target, slaving will slave MAV at the markpoint, not the TGP. Results in "MARK" in the SPI indicator, lower left of HUD, and "No track launch inhibit" if there's nothing at the markpoint Forgetting to make TGP SPI. Then slaving the MAV will point it at the wrong location, usually the current steerpoint. Forgetting to turn on Master Arm. I've never done this But, of course, all this is just guessing.

Yes, the slew rate setting on the MAV page gets MORE sensitive as it decreases. Increase it to 8.0 for maximum precision

yeah, my understanding is that it will look the same as the Hornet, with that ghost vector

IIRC this has been reported as a bug or not implemented yet. I'd also point out that caging the VV kind of defeats its purpose in crosswind landings, but more power to you if you want to do it without the help

'Ergonomics' was a bad word in the 90's Among all the US 4th gen aircraft, the A-10C HOTAS was completely overhauled more recently, that's why it's more ergonomic. From what I'm hearing, sometime before Suite 4, you took command of HUD, MPDs and MPCD the same way, by pressing castle in, then in any direction. The long-press adopted for the MPD's and MPCD and for a brief time both methods work, but in Suite for, they got rid of the castle in for the displays and changed them to long-presses. Why they didn't do that with the HUD is beyond me. As a workaround, Joystick Gremlin has a 'Tempo' function to translate long-presses into a different output, you may want to poke around with that

IIRC, 'STBY' just means you don't have a Maverick profile selected. I also noticed you have not mentioned the magic word 'profile' that @Yurgon mentioned? Can you confirm you had a Maverick profile selected?

That is correct. Remember, you're designating the sensor's target, not a point in space. If it says TGP in the lower left corner of the HUD, your SPI is whereever the TGP happens to be looking that very moment. Edit: it also means if your TGP loses the POINT track, you're going to have a very bad day At least until you fix it!

I know, I just thought it was funny since I fly with a retired JTAC who always groans when he sees me with a bunch of CBUs

Nothing says CAS like CBU-87's!

That's a good one!

The Engine MPD page may have the ability to show some fuel data, but the manual says it's not implemented yet, so not sure how useful it may be. If it does, putting that up on one of the MPDs would be easier to see than looking down at the fuel gauge.

If you don't have the Mavericks profile active, the MAV page will say "SENSOR" to warn you, IIRC A track or video would be nice, especially one demonstrating that when you switch the STEER switch on the AAP to all the positions other than MARK, that the problem immediately goes away like you're implying

FWIW the WW Orion stick's alternate cams give you a pretty good choice between no center detent, strong detent, and barely palpable detent. They're not cheap, but worth getting to play around with if you have other stuff to order from them! AFAIK VKB and Virpil have similar cam kits for their sticks

Cool beans! it's nice to have some perspective on its authority, thanks!

If you are successfully POINT tracking a moving target and the SPI is from the TGP, any other slaved sensors will follow the TGP's moving point. Of course, if your POINT track loses the vehicle, it doesn't help much AAA has a max altitude of about 8000' and a range of about 1+ miles. APKWS has a range of about 6 nm, Maverick's about 10 nm, so either work fine. Guns are doable with some nads or foolhardiness I don't believe the in-game JTAC can lase moving targets, but not 100% sure

Yeah, the clinically pedantic like me would clarify whether something is 'full-authority' FBW or not, but I think when people talk about it that's what they usually mean. The description of the F-15 CAS is that it gives you "limited" aircraft control as opposed to "very limited" without the mechanical controls. Not that those are terribly technical terms, but I'm guessing few people would volunteer to test that a plane with the mechanical controls intentionally removed

I refer you to Mr. Laobi