dporter22

Anyone know what 'Image Capture' (Left Throttle Button Long) does exactly, and has anyone ever figured out how to easily assign a long press to a HOTAS control if I'd like it to do something other than capture an image?

If you fire 3 Mavs from one station, 1500 +/- pounds does make a difference though, so it would have been nice if there was a setting to alternate. It also would be nice if the station number for the active Mav, or any other ordnance, remained on the HUD.

I stand corrected, I was looking at Chuck's Guide (pg 224). However, there are errors or confusion in the ED manual also. For example, it shows Boat Switch FWD and AFT as black hot and white hot when it should be black crosshairs and white crosshairs (pg 93), it shows Mav China Hat FWD Short as Uncage/consent to self-track when it should be Mav FOV, and it shows Coolie Down Short as Swap MFCDs when it should be HMCS as SOI. Then on page 90 it has TAD DMS functions that don't do anything (Quick Toggle, Select TAD Centre Option, CEN/DEP Mode CNTR Own), the HMCS DMS FWD and AFT brightness functions don't do anything, and TGP TMS FWD Short says NR track when I assume it should be INR Track. Also, page 90 says TGP AFT Short is FLIR Auto Focus while page 522 says it's Return to INR Track. I could go on, but all the errors in the manual is a different thread.

Speaking of the Mav crosshairs, why does the current manual for the Mav Boat Switch say Light/Hot Dark/Cold for both the FWD and AFT positions? What does that mean and why are they the same?

That's my point, the manual is inaccurate/outdated/confusing which makes it frustrating for an average user when it doesn't have to be. Yes, it's a complex sim. Yes, ED is busy (and we thank them for everything they do). Yes, a few errors are to be expetcted. Etc, etc. But the point is that a user should be able to pull up a current, accurate, and fairly mistake-free manual rather than endlessly searching through third-party guides, trying to find releveant videos on youtube, scouring this and other forums for explanations and solutions, etc. Those other sources should be supplemental, the official manual should be the standard. It's not difficult to do. When you find and correct errors or make changes you simply update the manual and post a more current version. If you release a new Tank Killer version you post a supplement to the manual or make the changes in the manual itself. When you are working with stable and OB versions, you keep the manual accurate for the stable version and post separate info for OB users. For example, why does the current manual show HOTAS TAD functions that don't actually work (Select TAD center option, CEN/DEP Mode CNTR Own, etc.)? Or why does the Boat Switch for the Mav say Dark/Cold Light/Hot for both the FWD and AFT positions when what it really does is just change the color of the crosshairs? Is it because these are mistakes, or something that's planned to be implemented later, or only works in OB, or worked before but doesn't work now, or only applies to the Tank Killer, or because my controller isn't working correctly, or because I don't understand something, etc.? I have no way to know without spending a lot of time searching for the answer, when the manual itself should contain the answer. Again, I love the sim. This is just an area that could easily be improved which would really help a lot of users. And yes, I'd be happy to help write/proofread/review.

Not sure I understand your comment. You can adjust the boresight as many times as you want.

Also, even if I reference the other guides there are still confusing mistakes. For example, in the current Chuck's guide Page 211 says Coolie Up for HMCS as SOI, and then says Coolie Down for HMCS as SOI on the very same page.

Thanks Hawkeye. I guess I don't undertand stable vs. OB. It seems that stable should be exactly that, stable (at least reasonably so), while OB should be the less stable, more buggy, work in progress version. IMO a customer should be able to say, "I'll purchase and stick with the stable version because that's the one where most bugs have been worked out, where the manual is accurate, and where I won't have to worry as much about glitches and things that don't work." Whereas another customer can decide, "I'll use the OB version with the understanding that I'll get to try some new stuff, but I accept that there will be various problems and I might have to figure some things out on my own." Just my two cents from someone who loves the sim but who sees some things that could easily be improved for the average user.

And why is there not a way to edit the title so I can correct it from 'difference' to 'differences'?

Sorry if this has been covered, but it's a constant source of frustration that there are several mismatches between what the manual says and the sim. I understand that everything is a work in progress, however there should be a simple way for the user to figure out what actually works, which controls actually do what, which HOTAS functions only apply to the beta version, etc. Little things, like how some of the TAD DMS functions listed in the manual don't actually work (at least not in the stable version). Why isn't there a simple, current reference to check which errors have been corrected, differences between stable and beta, recent changes to functions/HOTAS assignments, etc? And shouldn't the manual and various guides be written for the stable version anyway? IMO, the stable version should be the standard, with an accurate manual, where new and old users can go as a definitive reference, while the beta version with all it's works in progress should be the one that may or may not be accurate and where users accept that there will be some errors. As it is now, it seems to be the opposite. In the operational world, whenver there is a change or correction, a message is release fleetwide and it's mandatory for every crewmember to update their pubs immediately.

IIRC you have to be in boresight mode to adjust the reticle. You are correct regading the sensor though, only the color of the crosshairs changes even though the manual says it changes WHOT/BHOT. It would be very helpful to have a WHOT/BHOT capability for the Mav.

There may be legitimate reasons for it IRL and I support ED in making things as real as possible, but from an ergonomics and human factors standpoint, when Aft Short is the function to recage or recenter in every other circumstance and for every other sensor, having it not do so for the TGP is less than ideal. I understand that's how it is IRL, but IRL isn't perfect either. As an aviation mishap investigator in the Air Force I've investigated dozens of crashes where the aircraft controls and human interface were causal or major contributors.

Yep, I see it. Another error in the manual then, becaue the manual has that OSB as TST.

Don't flame me, but I still hate that China Hat Aft Short doesn't recage the TGP like before, and worse, that you can't reassign it to do so if you want.

For anyone else who's unable to assign TDC Slew to the CH Pro Throttle mini stick, all you have to do is manually assign the axis instead of physically moving the stick.

For anyone else with this issue, all you have to do is assign the axis manually instead of physically moving the mini stick. Very simple but I didn't even think of it until someone else suggested it.

You've got to be kidding me - that was it! How could I not think of something that simple? Thanks bro!

Yes, I've moved the mini stick all around to the extremes. I'm unable to assign the mini stick to any other axis in any module. Here's something very odd; I'm also unable to assign it to HOTAS Slew in the A-10C Game or A-10C II Game versions. The mini stick is automatically recognized and assigned as HOTAS Slew only in the A-10C Real and A-10C II Real versions and doesn't work anywhere else. I don't dare unassign it and risk losing the A-10 slew function if it won't reassign.

The TDC Slew Horizontal/Vertical (mouse) options are grayed out, you can't assign anything to them.

CH Pro Throttle. There are no conflicts, all the other axes can be assigned and work properly, all other buttons function properly, there are no error messages, I've tried clearing everything and started over, and the mini joystick works fine in the A-10. The only thing I can think of is that ED hasn't implemented it in the F-18.

Yes, F-18 Sim. Throttle Designator Controller - Horizonatal Axis and Throttle Designator Control - Vertical Axis are supposedly the correct names, but double clicking on the applicable box in the Throttle column and physically moving the mini joystick to assign the axis does not work. The movement is not recognized and the control is not assigned. You can assign a hat switch up/down/left/right to the TDC Slew function, but that doesn't allow diagonal movement in order to smoothly slew the TDC around. In the A-10 module the mini joystick can be assigned and works perfectly for TGP/Mav/TDC Slew. I thought maybe TDS Slew using a mini joystick hadn't been implemented in the F-18 yet, but previous posts say it has been. Sorry, the link you included just takes me to a blank discord page.

Anyone?

Thanks, but that option doesn't exist for the F-18 in my controls page. There is Throttle Designator Controller which doesn't work, and TDC Slew (Mouse) which is grayed out and can't be assigned. In the A-10 it's HOTAS Slew and it works just fine.

Yep, option is unchecked. (I've tried assigning with the option checked and unchecked, doesn't make a difference. Still can't assign the mini joystick as TDC Slew.)

Anyone?