9thHunt

yes it would. Unfortunately, since Heatblur added some new key binds they had to over write your old ones. It wasn't really a surprise, IIRC it was in the patch notes.

Maybe it's because I don't own the Viggin, but what's wrong with the current tomcat theme?

IIRC, there was a chance of arcing in the thinner air at that altitude, which can cause a fire. Because the pods could not be jettisoned, the fire could spread to the rest of the aircraft, hence the altitude limit.

I'm not an expert on the huey, but yes, I'm pretty sure there is a gearbox and clutch that has to engage for the rotor to spin.

ok, I went through the manual, and tried again. I am still not getting anything in game. Oddly enough the VA log shows it recognizing at least some of my commands, but I get no feedback in the game. It doesn't start responding to me until I give up on VA and start using the ingame radio menu.

I will check the manual, thanks. I was using easy comms, so I didn't set the radio myself, I let the game do it. TBH, I didn't t think to look through the manual for a list of commands, and that might have been my problem, I think I might have said something like "Mother, Colt 1-1, inbound," I'll try "Marking Mom's."

according to the F-5E-3 Flight Manual included with the module, the maximum deployment speed is 180 KIAS

I've noticed this as well, on just about any mission where you start in the six-pack with your wingman parked next to you, (ie. the "Mission Qualification - Supercarrier Cold Start" mission for the Hornet). Your wingman starts rolling immediately after you do and immediately turns towards cat 1. If you're not quick enough to get out of his way, he will run into you. I've found that the best way to avoid him is to make sure your NWS is on high gain so you can turn to avoid, and just try to taxi forwards quickly enough to get out of his way. Usually, if I can avoid my wingman, this results in overshooting cat 2 and having to either loop around over the bow cat tracks or turn towards the waist cats instead.

Based on how detail attentive Heatblur has been thus far, and how DCS liveries are laid out in the game's directory I think they will come assigned to a given model out of the box. However, since they haven't said anything about a new paint kit, and the livery competition is asking for liveries of both models, I suspect that liveries for both versions will be cross compatible, it would just be a simple matter of copying the textures from the -A folder to the -B folder. You might just run into trouble with textures of components that are not part of one model or the other, like the Ali-Cat not being equipped with drop tanks.

funnily enough, now that I've called attention to it, it's not happening anymore. I've flown a couple of times since yesterday and it's reading right on now.

That might be a deal breaker for me, as handy as it might be to talk to Jester directly, I feel like, at least while I'm learning the ropes with the software, I need the wheel to know what my options are. There's no way to make this optional? It should be installed as per the instructions, I will try to post that log file the next chance I get. I also can't seem to get it to talk to the supercarrier correctly, It made the default Inbound to land call, instead of the SC's special inbound call, and would not advance to the rest of the dialogue chain, nor could I get it to respond to "See you at 10," "Tomcat Ball" or anything else in that dialogue chain.

I have the AIRIO plugin, but I can't get Jester to respond to any commands, and it appears to have disabled the Jester menu as well, because that no longer comes up when I press the hotkey.

ok, here's a link to my thread: https://forums.eagle.ru/forum/english/digital-combat-simulator/dcs-supercarrier/bugs-and-problems-bl/291825-reported-no-comms-after-bolter The suggested workaround was to just go straight back into the landing pattern and use the hot key to call the ball at the proper time.

I noticed something funny in the Tomcat the other day. Whenever you give a fuel state on radio (i.e. during approach check-in with Mother), it's a couple of thousand pounds low compared to the actual fuel gauge in the cockpit. I also checked the Hornet, but didn't see any discrepancy there. Of course, for all I know it could be SOP for tomcat pilots to short their fuel states.

that said, as I posted in another thread a couple weeks ago, boltering can screw up the comms triggers on your next pass. Apparently because proper bolter procedures aren't implemented yet.

The Aerosoft F-14X is just the A and the B, just like Heatblur's Also, the AN/APG-71 is not identical to the strike eagle's AN/APG-70. IIRC, it is a hybrid of that radar and the AN/AWG-9.

the nose pitching that the OP describes sounds like Pilot Induced Oscillations. Those come from over-correcting. The only way around PIO is practice, you need to get a feel for how the aircraft moves and make smaller stick inputs to correct your flight path. Trimming the aircraft properly will help, because you wont need to make as many small corrections.

That is weird, there is no reason why it should not invert that input when checked, my old CH Pro throttle works fine in DCS (it does read as reversed, but checking the box does fix it.) Are you absolutely sure you set it correctly? Did you invert it in more then one place?

Rz is the name of the entire access, it doesn't matter if it's left or right. Try using the actual X56 software, I've found that it works better then the default windows config app.

Hmm, it appears that the wings aren't just swept back. If you look carefully they are overswept.

"Kiss off" is a hand signal to your wingmen to break formation and enter the pattern. (So named because the hand signal is blowing a kiss. Although I don't think it's animated like the salute.) You're supposed to use that one when you get signal charlie, if you have wingmen. "Hornet Ball" should pop up in the radio menu when you can see the ball on the IFLOLS and are within 3/4 mile. If you can't see it by then, that probably means you are way off glideslope. "Clara," is the call you would use if you can't see the ball in the groove. If you call "Clara," that does bypass the ball call, and the LSO will talk you down. As others have pointed out, the Hornet and the Tomcat do have hotkeys for the ball call, those work at any time.

Didn't they also use TER's attached to BRU-32s?

this mod worked, although I ended up extracting only the line for that command, just in case it was an out of date input file. Shagrat's suggestion looks promising, and is probably a better long term solution, since it wouldn't get broken by DCS updates, although it was a bit hard to follow because the post's image links were all broken. I still think HB should consider adding this bind to the default commands, since it obviously can be done, and the X55/56 is a popular stick.

the X56 throttle has a slider switch that is in approximately the same position as the speedbrake switch on the F-14 HOTAS (labeled as SLD), unfortunately, DCS only sees it as one button, pressed when the switch is in the ON position, meaning that while I can set it to extend the speed brake, it doesn't retract the brake when disengaged. Heatblur, I know there are lots of ON ELSE OFF type binds in the tomcat's control settings, would it be possible to add one for this? Barring that, does anyone know how to use the X56's programming software to make this work with the existing binds?

I could see this as a crew contracts option.