Arbil

I've been using a modifier in the Tomcat since launch with no problems. You guys sure you didn't accidentally set it as a toggle instead of the right type of modifier? When you click the modifier button both options are on that screen that pops up. You should be adding your modifier to the left list, not the right one.

I remember heatblur saying a few weeks they recommended not making custom load outs and only using the load outs she came with for now. Not sure if this is still the case or not.

I've been taking off from Vaziani then turning around and flying back towards the north west over the airports and lake. For whatever reason the issue is the worst for me here. I can post a video if needed but it seems like that's kinda redundant at this point. I had been using an old Dell 24 inch monitor up until yesterday and am now using a gsync ultrawide and in the little bit of testing I did last night it seemed like the flickering caused gsync to stop working. The flickering got really bad at one point and when it came out of that spell gsync wasn't working, had to alt tab it to get it back. Would love to see this issue resolved.

I tired having it bound to the encoder wheel on my throttle and when that didn't work tried just binding it on the keyboard. Get a CTD either way as soon as I try to adjust it with a binding.

I feel like I should be able to look over my shoulder while in F1/cockpit view and look at the wing glove lights and see if they are on or off. Doesn't seem to be the case now. I can see the light, but there is no change when turning it on and off. I can clearly see the light/s going on/off when in F2/exterior view.

+1 Both the ALR67 anbd ARC182 work correctly when bound.

For me personally, because I have a throttle with an adjustable detent, I prefer the way the tomcat works now as opposed to the f18. The f18 has a super dead zone at the bottom of the range near the idle detent that reads as nothing when you move the throttle. Wish it behaved just like the f14 does now instead.

How is that supposed to behave? For example, I bind the "Autopilot Vector ACL, else off" binding to a keyboard command but when I use that command it acts like a momentary. I have to hold it to get it to stay in the ACL mode and if I release it it switches back to off. Is that correct? Is that because that binding is specifically for a momentary switch? So if I wanted to bind it to 2 buttons, one for up and down, heatblur would need to add those options?

When my human RIO arms his and my ejection seats the mechanism on top of the seats doesn't animate for me (and if I do it vice versa for him) and if we need to eject I have to have armed both seats. When we are punching out only I can eject because of this and what happens is wild. I end up with my buddies pilot model in the RIO seat and the plane doesn't explode on impact and sinks into the map. I can then arm his ejection seat and he can punch out.

Pushing the stick forwards(nose down) doesn't use the full range of my joystick(T16000m). The virtual stick in the hornet reaches full forwards and stops moving and I still have about 1/3 of the play left in my joystick before it goes full deflection forwards. In the FCS page the numbers check out, the ctrl+enter overlay shows it reaches it's max, and in the actual controls/axis tuning menu it looks good. Is it like this for everyone in the hornet no matter what joystick you have? If so why? I don't like the way it feels having that dead area up there. It doesn't behave this way in any of my other modules (as far as I can recall, I only tested the p51 real quick).

Thank you very much. The image helped me understand what you meant much more clearly. I appreciate you taking the time to reply. I think I've got it feeling significantly improved now, thanks a bunch.

What you described here is not capable of accomplishing what I, or the person in the thread I linked, asked for, but thanks for the reply.

I would love the ability to be able to do this in DCS. I need to be able to set just the positive y value (pushing the stick forward) and negative x value (rolling left wing down) with deadzones. My stick is starting to feel really bad and being able to set the positive and negative values for each axis individually would make a gigantic difference for me. Edit: found another thread requesting the same thing from earlier this year. https://forums.eagle.ru/showthread.php?t=204104&highlight=Deadzone

Once I dirty up to get on speed I don't pay any attention to my airspeed number.

Ever since the FM update a couple months ago I have been having so much trouble putting it down on the deck. The best way I can describe it is that I am floating right before touchdown. Constantly. It even feels this way doing ground landings now. The slightest throttle correction to slow my decent rate seems to just send me upwards like a balloon that a child let go on accident. I can immediately go idle after that small correction and it seems like it takes a year to start descending again. I'm sure part of the problem is my frustration and part (of the carrier landings at least) is that I am really trying to get better at using the ball for throttle corrections in the last 3/4 mile and not just spotting the deck with the VV. But damn, ever since that last big FM change it has destroyed my ability to land the plane properly and I don't know what to do to correct it, even after hours of practice.

I have the left and right engine OFF/IDLE bound, each to their own button. When starting up I press the button and it comes out of OFF into IDLE and the engine starts up. But when shutting down the bind acts like a momentary. If I hold the button the engine will eventually spool down while the throttle is held in OFF position but as soon as I let the button go it springs back up into IDLE. Shouldn't that OFF/IDLE bind behave the same way when shutting down as it does on start up? As in when I press the button I have bound for Throttle (Left) - OFF/IDLE when wanting to shut down the throttle snaps and stays in the OFF position like it did to the IDLE position on start up? Like I could keep pressing the button and toggle between having the throttles in either OFF or IDLE?

Here is the new mission I made. Cauc_LowVisRainCaseIIIPractice.miz

I definitely do call ATC for inbound. I still get no lights during the day. I just went and double checked to be sure, made a new mission in the editor from scratch. I do get the runway lights lit up when I call in ATC at night (or dusk etc) but nothing when it's during the day and low vis like in Druid's video. ??

In Druid's second video, the ship having the deck edge lights and the island being lit up when he get's to about a mile out, is that something I should be seeing? My ship has no lights on. I only see the OLS. Trying to land with 1300ft visibility and the island being completely dark is terrifying.

Any tips or insights into this? Specifically the line up, vertical needle. I always find myself chasing it and can never keep it stable in the middle. If I had to rely on only the needles I would never be able to put it on the deck.

What is the temperature of the mission? I bet it's pretty cold ... https://forums.eagle.ru/showthread.php?t=213061&page=4

I am getting the same kind of thing. Tune comm 1 to preset 1, some ATC channel, I can hear ATC fine and comm 1 volume works properly to control their output. Then put comm 2 in manual and tune to an ADF/VOR. Now when I turn the volume down on comm 2 to turn the ADF morse volume down it also turns down the volume of my ATC on comm 1 and I can't hear them anymore unless I turn comm 2 and the ADF morse back up. Bug? My comms are set on easy comms, haven't checked how it behaves without using easy comms.

I prefer the way the AB worked before this last patch. It had logic to it in the sense that I could have a heavier jet launching and it go into AB according to that weight as needed. If the plane was light enough to not need AB, it wouldn't go in to AB at max throttle unless you had bound where you could pull the finger lifts and force the AB. That seemed like how it should work to me. After this last patch if the AB detent option is checked you have to use that key binding to pull the finger lifts to go into AB anytime you are WOffW. It doesn't feel good. But if you go the other route and deselect the AB detent option the only way to launch a light jet without AB is to manage the throttle carefully and that doesn't feel great either. Again, I feel like it was working perfectly before the last patch, my two cents. I am not using a throttle with a detent/warthog, by the way.

Created a thread in Bugs. https://forums.eagle.ru/showthread.php?t=213061

Cold weather, cold enough to snow, carrier launches fail. Try to launch on the Caucasus map (only map you can get the temp low enough to repro this) with the temperature low enough for it to snow, I did -1. You only go off the deck at about 130. Moved the temp up to 8 (chosen randomly, didn't test the threshold) and launched just fine, about 200 leaving the carrier. The following link is my initial post in the parent f18 forum. In post #20 I link to 2 other threads I think are the same issue. In post #22 user kk0425 posts tracks that supposedly (I didn't watch) demonstrate a cold weather fail and a warm warmer weather success. https://forums.eagle.ru/showthread.php?t=212287&page=3 [Launching into the water?] (page 3 has the tracks)