Raisuli

Is this a test? Do we get a stuffed Air Force pilot if we guess right? Is she outrageously intelligent and worth spending a few hours buying drinks and talking with? I'd love to get some quality chat time with a female military pilot for a project I'm working on... :) Some data might be useful. Start with the monitor setups, extend that into ~/DCS World\Mods\aircraft\FA-18C\Cockpit\Scripts\Multipurpose_Display_Group\Common\indicator\MDGstrokesDefs.lua (I think that's right, anyway).

I will never abandon my I-16. When you get tired of electric jets the I-16 is a breath of fresh(ish) air with that open cockpit. I'm Navy so I never got the silk scarf, but it's still awesome. Some day I'll get energetic and figure out how to actually land one. From the reports on this forum she's (he, actually. I believe they're referred to by the masculine) quite a beast on the runway in both directions.

Great stuff. Ok, no APKWS for the F-18... ...but what about the F-5E-III? (sorry, couldn't resist) I'm honestly pretty ambivalent about this; there's already so many things to drop off the F/A-18s wings already. Whatever needs doing there's probably a way. If not, there's the A-10. If that can't kill it, on to the MiG-21...

According to BAE this is a screw-on addition. Set the laser code on the guidance section and slide it into the tube. There's no modification to anything but the missile itself. If you have a hydra pod and a laser you can use APKWS. (this was from a different thread):

The inability to map MFDs is looking less and less uncommon.

Are the MFDs completely greyed out? We might be able to fix that... Control Panel > Devices and Printers Right click an MFD > Properties Select the Hardware tab Click Properties Select the Details tab Under Property select Hardware Ids from the dropdown box Note the IT. In my case HID\VID_044F&PID_B531 In Regedit: Go to Computer\HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM Select that Hardware ID Right click OEMName and select Modify Change the name. I used F16 MFD 3 Go to Computer\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\MediaProperties\PrivateProperties\Joystick\OEM Same deal. Select the Hardware ID, change the OEMName to the same name you used above I don't know if a reboot is required at this point, but that's the best way to be sure the HID devices are all re-read and registered Fire up DCS and see if that device is usable in the A-10C II See? So simple, I can understand why ED doesn't think this is a problem.

I'm trying to understand why you're having trouble binding them. It was like binding anything else; double click the control on that controller, press the button. There's magic you can do in the registry to get the LDDI and RDDI working, and they work again. It's beyond crazy ED makes this so hard. The only modules affected are A-10C, A-10C2, and AV8BNA. The A-10A doesn't have this problem. The other interesting thing is how studiously BN and 9L are not saying anything about it.

That REALLY blew everything up. Now the A-10C II will only allow me to use one of the three. This is becoming very annoying (and probably one of those minor things the mods pretend don't exist). <edit> It gets better...now I can't use ANY of my MFDs with the A-10. This is awesome! </edit>

Yup. Left switch became ARM/SAFE and right switch whatever that was. The A-10C was the first module I bought, but for some reason I was drawn to the second module, which had a pointy nose (F-5E), and I still don't remember the nomenclature for the gun/stability augment switch. :) I really got into DCS for the F/A-18, but it was pre-order so I had to wait quite a while for it.

From my perspective this seems like something arranged between Thrustmaster and DCS. I've heard the TMWH was released specifically for the A-10C, which may not be true. If it is then only allowing the module to talk to the Thrustmaster hardware in a specific way seems like the sort of provision you would find in a contract like that.

Worked for me (at least on the MFDs the A-10C II has blessed as appropriate for use).

Still happening as of Sept 30 as well (without so much as an ack, which is why I don't often report bugs.

Nice call. It's a bit concerning, though, because left and right MFDs were both "F16 MFD 1" even though they're different names in DCS. They also have the same hardware ID. I changed the names from F16 MFD 1 to F-16 MFD 3 using regedit, and when I restarted DCS the two F16 MFD 3 devices were there, and in the A-10C II it was now the AMPCD it won't let me use. Which is semi-fine. I will need to re-bind all three MFDs in the F-18, but it recognizes all three and I can assign buttons (I think; nothing is greyed out). The question is why A-10C II is blocking one of the three MFDs? It's not that they have the same hardware ID (two of the three do, the F-18 is fine with it, and the A-10C II is using the two with the same ID now). There's something else odd about this new module's controller code.

It's almost like flying these things is a full time job or something :) I'm going to pay far more attention to WP 0 in the future. Since I generally air-start (too lazy to fly all the way to the trigger zone) that will give me something to do before I hit the RangeHot trigger, but my guess is I've ignored the FPAS and waypoints for too long. <edit> Ran a mission to take off from Ramat David, transit to the CV, then launch and return to R-D. This time I paid attention to all the points everyone has made, and the whole thing is making better sense. Boltered my first attempt and got Home Fuel, set home to 59 (null), circled around and trapped (4 wire, no grade, EGIW - my favorite trick), had no arrows using 59, so I set it to the north geographic pole, and the arrows magically appeared. Just like you guys said it works. Fought with MFDs on the new module and mucked up my F/A-18 a bit, so more playing with navigation tomorrow. Probably more CQ as well, because I'm really rusty. </edit>

The view does seem pretty close. I noticed that right away, and assumed my zoom was too far in, but it was on the center detent. Played with it, and it still seems a little close. Cockpits tend to be pretty tight, though, so maybe that's what pilots really get for field of vision?

I thought WP 0 was automacigally the point where the aircraft starts, and invariably I get no arrows at WP 0. I also get HOME FUEL (usually as I'm turning into the groove or right in the middle of a bugfight) with it still on WP 0, but the arrows re-appear once HOME FUEL is annoying the crap out of me. deedle deedle. deedle deedle. deedle deedle. deedle deedle. Wave off, wave off. Get the heck away from my boat. I think the Air Force needs pilots...

I have three TM Cougar MCDs backed by LCD panels. LDDI, AMPCD, and RDDI (one guess which aircraft this is set up for). The Left and Right MCFDs are automatically displayed on the LDDI and RDDI respectively, which is exactly the desired behavior. The left MCFD controls were mapped to the LDDI buttons without issue, but when I tried to configure the right MCFD to use the RDDI buttons they were greyed out. The only MFD that the right MCFD is allowed to map is the AMPCD, which is in the middle of the setup and isn't the one with the right MCFD displayed on it. This is more than just a little bit annoying; I can't even understand why you would restrict the device that can be mapped to a specific control in the aircraft.

Fine. Everyone is talking about what an amazing mod this is; time to get the ground grew to dust one off and get it fueled up for a hop. I'm going to borrow your mission, if you don't mind!

I'm not entitled to an opinion, so I'll go with the guys who've been there and done that as well. It makes me curious what docs DCS has to the contrary. There's no way I'm going to say anyone is wrong. Who knows, maybe someone made an alternate harness for some reason 13 years ago and it wasn't widely used? Is that a possibility?

Gah! Any time you 'know' you're right it's time to check...you guys nailed it. I've been flying a mostly clean ship lately, doing guns only engagements and learning how (not) to refuel and collecting wave-off tokens. A clean F/A-18 can supercruise above around 15k and it's very fast below that. I've been pushing the speed limit, as you say! :thumbup: :joystick: :pilotfly:

I have you bookmarked; there aren't many who are. Thanks for the new tutorials!

Uh...I don't think so? That's pretty much ALWAYS up on the DDI. I know the settings for "home" don't exist most of the time until I get the HOME FUEL deedle every two seconds. If I'm really, really fast I can sometimes set that when the mission first starts, but then the option vanishes.

Paypal worked for me, but it was slow enough to make me wonder. Probably busy :thumbup:

I thought the 'experts' telling actual Naval Aviators they're wrong were bad. I bet those guys want to go back and slap their flight instructors and squadron COs for misleading them this whole time. On the other hand, as far as I know (and I don't know much) the F/A-18C only carried 10 AIM-120s once for a test and photo op, and we do it every day here. As an SMM (subject matter moron) I love it when the SMEs are willing (and able) to share, though. I've learned a lot about the reality of air operations here.

...someone thinks I'm going to get work done when there's a new module queued up on the sim? Seriously? ...AND they fixed the AIM-9 on the Murder Hornet. Watched a track of an AIM-9X shot and the missile went straight into the ground. The MiG-29 that was killed the first time flew off and was lining up for a shot of its own when the track ended. I should have flown back to the CV, just to see if I got shot down in the alternate universe of the track file.