JIGGAwest

This is probably all personal preference. I suggest using whatever you think is useful. I dont use all the trigger functions, but on a few aircraft I do. for example: On the Huey. I use the "flip down" trigger function to switch to rockets, with the pull being the rockets fire button. On the harrier and the f18, I use the flip down to switch Air to Air gun mode. On the BF109, and the Viggen I use the "flip up" to arm the guns/weapons. As these aircraft have something similar to this in game. I'm sure others have more effective uses for these, but this is what i do.

Hello Devs and community managers!! Thank you for all your hard work. I appreciate your consistent efforts perfecting this work of art! I was wondering if you would consider implementation of moveable and resizable UI layers. Current issues I have with a multi-monitor setup with exported MFD's. This monitor setup is setup has one monitor underneath the main monitor. Huey multicrew crew control UI layer is programmed to appear in the bottom right of the full DCS render screen. With This multi-monitor setup the UI layer appears off screen and incorrectly sized due to smaller screen resolution for the second monitor. Equal sized monitors wouldn't have the exact issue, but would the UI layer would still appear off screen. The controls UI layer appears top left, which is ok in this setup. The Mi-8 and mi-24 autopilot controls appear top right Which is ok with this monitor position. The petrovich menu for the pilot appears in the lower center position rather than true center, which is because the lower monitor configuration. Any other monitor location would cause similar issues due to the UI layers being in a fixed position to the total render size(dimensional positions). A possible fix would be to have to UI layers only overlay on the main display screen. But moveable and resizeable UI windows would probably solve all the issues with multi monitor configurations. thank you for you consideration

Do you see both sets of crosshairs on the HUD? Do you have switch #1 and #7 up (on) Do you also have switch #1 up (auto) Possibly #2 needs to be up (sync)

I can confirm they are working. Did a cold start in dark yesterday. Can't remember if I pressed a specific switch. There are switches for the cabin lights at your left elbow at the top left of the panel. One is covered. Not exactly sure what they do. There are 3 brightness dials at your right elbow at the bottom right of the panel. They have like 10 clickable positions. There are also 2 or three more dials on the bottom right front panel near your right ankle. Try those?

Is there a way to recenter the petrovich menu? The position of the petrovich menu seems to have moved to my lower half of my screen. I use track IR. I have to look way up to point to a target near the HuD. Sorry I'll post a screen shot or track later today.

Would you share where to place this code within the simshaker.lua? would one just copy and paste anywhere? Or are you indicating the line numbers for where to place?

@=Andre= Is there anything we can do with the new module Mi24 (Hind) to make the sound module work? Or will we have to wait for an update?

THANK YOU !!!

I have been having trouble importing more than 2 target points using the F10 map marking function. Additionally If there is another Harrier on a multiplayer map I am importing their target points. I'm using the target point naming convention T01 T02 T03 full track file 18.1mb https://drive.google.com/file/d/1qv9GXmse0udeV1O9PJvQy59q5Jrrn9u7/view?usp=sharing

having same issue

I have to add to this original post. The latest update has pretty much broke the Harrier exported MFD's for my setup. There was a fix working, I was using, and I could deal with it at that point. Someone posted a MFD readability fix in the user files section, but this no longer works with the latest update. The imaken fix still works for me, but It will break the hot spot indicator from time to time requiring a slow repair of DCS. again my display setup; Windows10 display settings: display 1 3840x2160 120hz - 10bit RGB HDR on, scaling 100% display 2 1920x1080 60hz - 10bit RGB SDR, scaling 100% dcs render settings 3840x3240 monitor setup LUA: _ = function(p) return p; end; name = _('MultiscreenBEST'); Description = 'Multiscreen MultiAircraft' Viewports = { Center = { x = 0; y = 0; width = 3840; height = 2160; viewDx = 0; viewDy = 0; aspect = 3840/2160; } } UIMainView = Viewports.Center --///////////////// -- BLACK SHARK - Shkval --///////////////// Shkval = { x = 10; y = 2655; width = 700; height = 486; } --///////////////// -- COMMON MFCD-CENTER --///////////////// CENTER_MFCD = { x = 801; y = 2160; width = 426; height = 461; } --///////////////// -- COMMON MFCD-RIGHT --///////////////// RIGHT_MFCD = { x = 1215; y = 2540; width = 700; height = 700; } --///////////////// -- BLACK SHARK - ABRIS --///////////////// ABRIS = { x = 1295; y = 2540; width = 553; height = 700; } --///////////////// -- COMMON MFCD-LEFT --///////////////// LEFT_MFCD = { x = 10; y = 2540; width = 700; height = 700; }

also having the issue. AMD card... This issue is persistent in the latest update 2.7.1.6709 reboot of game does fix the issue at times. There have been a few times slow repair is required.

I'd say fly it! What mission type do you like? Or anything that you want to try? IRMav's can be a bit tricky. CCIP and auto bombing should be straight forward. Laser guided bombs and JDAM's have their sequences you have to get used to... I think the biggest changes have been TPOD Hotas commands and the SSS. I could link the older version of chuck's guide if you think that will help.

Look at this nose dip on the harrier before landing. That thing is pegged in the air. I don't think we have this much thrust on the nozzles.

I have a virpil throttle. I originally followed @imacken guide in the Virpil section of the ED forum. do you have physical detents set up on the throttle? Have you set the deadzone for the lower detent? You should use x saturation for the high detent. Verify it works by the axis tune chart or the axis config screen. Make sure the white line moves full end to end. I also use the Virpil software axis to button for the throttle cutoff switch. Which should be below your bottom detent value. Mine is a deadzone of 5 based on the 5% in the Virpil software throttle position. My axis to button is 3-4% setting in the Virpil software. Bind that throttle movement to the cutoff switch. let me know if you need more help.

It works at night for me. I don't know the effective range. But lower altitudes seem the only viable option at the moment when looking for ground targets. I had one instance where it was not working at all. I deleted the aircraft and ran a dcs repair and it was fixed. But this was a few updates ago.

True, it may be more realistic in terms of weight effect on engine performance. Prior to the recent update I would almost exclusively vertical land with low fuel and empty ordinance. Engine performance has changed in my subjective opinion, and is more Difficult. I believe the current state is under powered for vertical landing and STO. Transitional lift and power seems to down quite a bit. I have no onions on realism, except for what I've seen at airshows in person. The real harrier seems to be much more powerful.

could you link this by chance? I don't see any mods by user TAZ in the ED user files.

I was mainly trying to confirm you have the correct binding. But, the first reply to your post said that you need to be in Master Mode Air to Ground before CODE will appear on the EHSD page. There isn't a A/G OSB. I suspect this might be part of the issue? I don't see in your list of procedures that you confirmed A/G mode ON. See if these references attached will help

Hello DCS devs, I'm not sure if this has been asked for before or yet. It would be nice to have a quit DCS confirmation "are you sure?" Option to enabled or not enabled. Quite a few times I have mis-clicked quit and lost progress deep into a mission and there is no way to recover that mistake. Thanks again for the great product! Thank you for reading my wish

I was having trouble with this too. With my CM3 I've set throttle cutoff and idle as separate logical buttons for the throttle position. But these Viggen controls don't seem to behave the same. It seems as if the two controls for fuel (Hotas cutoff and throttle to idle) are toggles, Instead of positive ON or OFF. Which aren't clearly labeled in the controls or possible implemented incorrectly. I believe I also settled on just using the off/idle only and it seems to serve the purpose fine.

You are saying TDC down. Do you mean SSS down? Or are you referring to TDC Depress (action)? These are two separate functions.

The TPOD laser shouldn't switch to safe after dropping a bomb. But you may have to press FIRE again to arm it. It will be boxed. Are you doing something after you drop a bomb like the previous poster asked? Review of TPOD startup: I'm not sure these are the culprits. But do you have the DMT switch on and the FLIR switch on that's near the NAV alignment knob in front of the flight stick? Are you seeing F-NOTRDY on the TPOD screen? Wait 3 minutes for TPOD cooldown.(warmup) To enter TPOD mode from the main AMPCD, you press TPOD, then STBY on the right. Then press the SAFE button to switch to ARMED. Press TRAIN to switch to LASR. Then FIRE. FIRE will be boxed when active. I've made mistakes in the past with the TPOD pressed on the AMPCD without pressing the STANDBY button. It won't switch to Arm until the TPOD is up(pressing the STANDBY button). Also check A/G mode and Master Arm ON. You can review Chuck's guide page 170 and 171 for step by step with pictures https://www.mudspike.com/wp-content/uploads/guides/DCS AV-8B Harrier Guide.pdf

i was getting a CRC16 CFG error with my CM3 throttle on a 15ft USB 3.0 extension. Added the throttle to a 3ft hub plugged into a 4ft powered hub, seemed to solve the issue.

@imackenWith your method I've been able to successfully do the following: I'm using your suggested Classic physical detents at their respective maximum positions. Ie the forward detent all the way forward and the back detent all the way to the back. My virpil software min / max % to physical detents are 5% and 78% I'm able to tune the F18 to the physical detent for afterburner. Push past the detent, i get afterburner. For me F18 is Deadzone 4, X Saturation 99 - you might have your forward detent not full forward compared to me? Not sure why there is much difference between our configs. - are you using separate left and right throttle control? I am, maybe that's the difference. I was also able to tune the Harrier to operate within both detents for 0-100% throttle. I didn't find it necessary to push past a detent in this aircraft. For harrier Deadzone is 5 and Saturation 75 But with the Mig29 FC3, the X saturation doesn't seem to work the same. Using separate left and right engine throttle. I might be thinking this is why I'm having an issue. I'll have to test this with single throttle control. For Mig29: Deadzone seems to set how close to the idle position is relative to the Virpil throttle throw. For example if I set a higher deadzone the throttle doesn't touch the physical detent before it reaches idle. X Saturation seems to only adjust the rate at which the throttle moves in game to 100%. For example if i set two different X saturations for left and right throttle, The throttle axis tuned with the lower X saturation value seems to shorten the in game throttle movement to 100%. I cant get a afterburner to line up with the physical detents with any setting. Maybe the separate throttle control X saturation works differently? Maybe FC3 X saturation also has different function. What is the X saturation supposed to do? Maybe that's why I'm a little confused here...