fael097

if it's a small bank then it's wind, the slightest wind will make it bank in dcs. I've never flown myself a real plane but I'd assume that if trimmed properly, a plane would be able to fly straight without auto heading or constant pilot input. that never once happened to me flying the dcs warthog and hornet

interesting use of an ipad. is it possible to do the same with a ms surface tablet?

alright, fantastic. thank you so much

+1 for having this in game.

glad at least one other person still didn't give up on this one lol

thanks for the track file rob

+1!! the current setting works if you assign it to the slew control I suppose, but an option to have it assigned to sliders is absolutely needed the way it currently works, you're better off assigning radar elevation to something like the boat switch than burning a spring loaded axis with it. the only difference of having it assigned to an axis instead of buttons is that you can change the speed that the elevation arrow moves, it's a waste. if you had the option to control it with an absolute axis, then you could assign it to the friction slider on the WH which is pretty much useless for the hornet, and have a proper behaviour for it

shouldn't this work as a slider instead of an axis that returns to the center?

this is exactly what I needed. yeah I know it's not an axis, but I had the buttons 29 and 30 assigned to "Throttle Finger Lift (L/R) - UP/DOWN" instead of "Throttle(L/R) OFF/IDLE". in fact if you select the HOTAS category when assigning controls, you'll only find the finger lift controls, not the throttle idle/off for some reason, and that's what got me thanks man

everything I mentioned has up and down values assigned, I wouldn't bother trying to sync a toggle switch that works as momentary.

ah, that's it then, I'm on stable, not open beta. thanks all

I see, but I don't really care about this as I have any problem with the afterburners, the problem is going from idle to off. I guess the problem is the same, but still

hey, thanks. I had a bit of trouble finding what is the name of the thing I should assign a keyboard command, but I found it, it's called "save cockpit angles" and it's RAlt+0 by default, and I'm not sure why it has this name since it only saves the zoom level that's stored in the zoom normal command. for some reason it also changes the default view where the game starts, it seems that the default view is an offset of this saved zoom level for some reason, really weird. so I guess you can't change the default startup view so I don't have to "zoom normal" every time I start up the game huh

dumb question but somewhat related: how do I update the hornet module? my jhmcs isn't showing up

no I didn't, I just had a curvature of 10 on the throttle axles and the afterburner detents worked fine. I just set this detents option on and didn't notice any change, afterburners are engaging at the same place, not sure what this option does. and the idle/off detents still aren't moving the virtual throttle into off, it just moves the virtual finger lifts up, which is my issue

I'm suggesting this not only because it's something that bothered me for quite a long time, but also because it's a shame that after all this time it's still working this way. I got specially frustrated with it this week since I recently bought the hornet and was trying to set up it's commands to my warthog hotas for the last few days, so I decided to make a wishlist suggestion as this issue has never been addressed. assume I'm only talking about commands for toggle switches (those that turn on when there's active input, and turn off when there's no more input) not commands for push buttons or keyboard (which turn on when there's input, and only turn off when there's another input). the way I see, currently the "hotas sync at startup" option works like this: so with hotas sync turned off (or probably before there was even the sync option) when you started a mission, the game wouldn't recognize any inputs that were activated before the mission loaded, so if you had a toggle switch in your controller set to ON before entering the mission, for some reason the game wouldn't know, even though the switch is constantly sending input. this is a bad thing because if you have some in game command that is set to ON by default on mission startup, and you assigned it to the mentioned toggle switch, when you want to turn the command OFF, you flip the switch to OFF, but there was no recognized input at first and there's no input now, game thinks it went from nothing to OFF so nothing happens. then you flip it ON and it "works", but the command in game was already ON, so nothing happens again. it only works the third time you flip the switch, when the game recognizes that controller input went from ON to OFF. best case scenario you would start the mission with your toggle switch set to OFF, then you would "only" need two flips for it to work. So without hotas sync, there was no way to make a game command that starts at the ON position work with a toggle switch on the first flip, only commands OFF by default at mission start would work right away, and only if you had your toggle switch set to OFF as well. So the logical thought would be making the game recognize input at mission start if there is a toggle switch set to ON. and this is how I believe that hotas sync works right now, that's the only thing it does, and this works for the worst case scenario, it properly recognizes your first flip as from ON to OFF and turns off the assigned command. but what if you start the mission with this switch flipped to the OFF position, while the game command still starts on ON by default? if it worked properly, hotas sync would have to sync all your assigned game commands to their relative toggle switches positions, regardless of what they're set to, and ignore the default state of this command, and update it to OFF as soon as the game starts. but that's not how it works right now, if you start the mission with a toggle switch turned OFF, it won't do anything since it's not recognizing any input, and the assigned command will still be ON by default, so you still have to flip the switch twice. to me, fixing this sounds as simple as setting the assigned commands to OFF if no input is detected. if I got this wrong please correct me, but I tested this extensively with the hornet, and regardless of how it works, it doesn't work properly, it won't do what it was designed to do which is sync your toggle switches to whatever they're set to, and this really should be fixed.

After 4 nights struggling and trying to figure out a nice profile layout, it's done and I just wanted to share it, maybe I still can improve it, or it could be helpful for someone else. I made this cause none of the existing profiles I found, be it on guides, youtube, user files, forums, none of them felt right, intuitive, or simple enough. some key aspects I tried to follow: 1. closest possible to the real hornet hotas 2. no modifiers and/or long presses BS 3. avoid leaving unassigned switches, only trigger first stage is unused, maybe it will get a purpose in the future 4. only assigning essential functions, or commands that need to be used on fligh, or have impact on the hornet's behavior. I tried to avoid assigning stuff that you only use on startup, such as battery, fcs bit, oxygen, etc. it's not like I can do a full startup without using the mouse so just the essentials assigned to the hotas. it's worth mentioning that I assigned to my mouse lateral buttons: VR zoom, esc menu, and the mouse pan view thing on/off, in case I'm not in VR, which happens quite often when you just want to hop in to the game to configure stuff, or test something quickly, and don't want to go through the hassle of putting your vr helmet or trackir clip for that matter. I assigned the speedbrake to the boat switch instead of the regular switch because I don't really like the different momentary/toggle behavior for deploy/retract, and I also needed a momentary switch for the catapult hook up command. on the opposite end I assigned the wheel brake because I'm using improvised rudder pedals, and it's hard to brake on them. I suppose this could be changed for people with proper toe brakes oh and I had to add some custom inputs to the joystick's lua file so the toggle switches would behave properly. I have to check the "hotas sync at startup" thing AND flip all switches to their assigned commands' default startup position so they all work on the first flip when starting a mission. this was also taken in consideration when chosing what to assign to which switch. if you're replicating this profile, you'll need to add this code to your joystick's default.lua file (located on C:\Program Files\Eagle Dynamics\DCS World\Mods\aircraft\FA-18C\Input\FA-18C\joystick). add these lines above the CHEAT section. I've put all of these custom commands into a new Mods category so they can be easily located in game. after that, just assign you hotas switches to these commands as you would do normally with any other. --------------------------------------------- -- Mods ------------------------------------ --------------------------------------------- { down = hotas_commands.THROTTLE_EXTERIOR_LIGTHS, up = hotas_commands.THROTTLE_EXTERIOR_LIGTHS, cockpit_device_id = devices.HOTAS, value_down = 0.0, value_up = 1.0, name = _('Exterior Lights Switch'), category = {_('Special For Joystick'), _('Mods'), _('Throttle Grip'), _('HOTAS')}}, { down = extlights_commands.LdgTaxi, up = extlights_commands.LdgTaxi, cockpit_device_id = devices.EXT_LIGHTS, value_down = 1.0, value_up = 0.0, name = _('Landing Gear/Taxi Lights Switch'), category = {_('Special For Joystick'), _('Mods'), _('Left Vertical Panel')}}, { down = gear_commands.AntiSkidSw, up = gear_commands.AntiSkidSw, cockpit_device_id = devices.GEAR_INTERFACE, value_down = 1.0, value_up = 0.0, name = _('Anti Skid Switch'), category = {_('Special For Joystick'), _('Mods'), _('Left Vertical Panel')}}, { down = gear_commands.LaunchBarSw, up = gear_commands.LaunchBarSw, cockpit_device_id = devices.GEAR_INTERFACE, value_down = -1.0, value_up = 1.0, name = _('Launch Bar Control Switch'), category = {_('Special For Joystick'), _('Mods'), _('Left Vertical Panel')}}, { down = iCommandPlaneGearUp, up = iCommandPlaneGearDown, name = _('Landing Gear Control Handle'), category = {_('Special For Joystick'), _('Mods'), _('Left Vertical Panel')}}, { down = gear_commands.HookHandle, up = gear_commands.HookHandle, cockpit_device_id = devices.GEAR_INTERFACE, value_down = 1.0, value_up = 0.0, name = _('Arresting Hook Handle'), category = {_('Special For Joystick'), _('Mods'), _('Right Vertical Panel')}}, { down = fuel_commands.ProbeControlSw, up = fuel_commands.ProbeControlSw, cockpit_device_id = devices.FUEL_INTERFACE, value_down = 1.0, value_up = 0.0, name = _('Probe Control Switch'), category = {_('Special For Joystick'), _('Mods'), _('Left Vertical Panel')}}, { down = gear_commands.EmergParkHandleOnOff, up = gear_commands.EmergParkHandleOnOff, cockpit_device_id = devices.GEAR_INTERFACE, value_down = -1.0, value_up = 1.0, name = _('Parking Brake Switch'), category = {_('Special For Joystick'), _('Mods'), _('Left Vertical Panel')}}, { down = cpt_commands.CanopySwitchOpen, up = cpt_commands.CanopySwitchOpen, cockpit_device_id = devices.CPT_MECHANICS, value_down = 1.0, value_up = -1.0, name = _('Canopy Control Switch OPEN'), category = {_('Special For Joystick'), _('Mods'), _('Right Wall'), _('Systems')}}, { down = ctrl_commands.WingFoldSelect, up = ctrl_commands.WingFoldSelect, cockpit_device_id = devices.CONTROL_INTERFACE, value_down = -1.0, value_up = 1.0, name = _('Wing Fold Control Handle TURN'), category = {_('Special For Joystick'), _('Mods'), _('Right Vertical Panel')}}, I think that's it, any suggestions? cheers

I'll post a track file later, I'm on single player, instant action, caucasus map, the ready on the ramp mission, but really this isn't hard to reproduce, any map, any mission will do. specs on my sig

ok... new question, what's the command to move the in game throttles from idle to off position?

absolutely not. I just tested and it works exactly as I mentioned above. so the 2 position physical switches on a controller only have one input, and it's either on or off. the launch bar and the anti skid virtual switches (for example) both start the mission "ready on the ramp" on the up position. if you assigned either of them to a switch on your hotas, and you start the mission with that physical switch on the off position, dcs won't recognize it and start the game on the UP position anyways. if you mod your lua file and invert the switch behavior, so that physical switch ON means anti-skid OFF, and you start the game with physical switch ON, then it will work, because the game recognized controller input, and anti skid will start on OFF position. if you do the opposite, and start the mission with the switched turned OFF, game will start correctly with the anti-skid set to ON, not because it synced, but because it didnt recognize input and started in the default position anyways. this is the behavior that got me wanting to manually rotate my physical switches 180º, but it's a stupid thing cuz it would only work for switches that start on the ON position by default, and the moment you decide to reassign that swtich to a command that starts OFF by default, it wouldn't sync properly again. is such lazy programming, they made this hotas sync thing only recognize active inputs, when you just had to program another line saying if no input is detected, assume switch is down. but anyway, the best way to go is leave the hotas sync setting on, and then flip all your physical switches to match the default mission start position. this sounds counter intuitive, but it's the only way to make all of them work on the go. one would assume that if you have the switches the same way the mission already starts, then you don't need to sync anything, but absurdly enough nope! if you don't have hotas sync on, then when mission starts, it doesn't care about any switches set to ON, and assumes everything is OFF. so if you have a switch assigned to anything that starts on ON by default (for example anti skid again), and you start a mission with the physical switch flipped to ON, then you will have to flip it 3 freaking times to have the anti skid flipped to off!!!! how can you program a fly by wire flight model and not be able to detect if a switch is on or off? ps.: please don't take me wrong, I don't mean to be rude or anything, dcs is the best flight sim I've ever played by far, and I love every aspect of it. I just think is such an easy thing to fix and it would really make things easier for setting up and customizing switches. in fact I'm just gonna add a suggestion to the dcs wishlist, if anyone else is annoyed by this issue, jump over there and give it a +1 wishlist thread: https://forums.eagle.ru/showthread.php?p=3683217

I assumed the zoom normal command would return the zoom level to the same that's used on mission start, where you can see the whole hud glass and the DDIs, but nope, zoom normal is closer to the front dash, it cuts a little of the hud above and the ddis below. in fact, once you change the zoom level, you can't go back exactly to the default zoom level that mission starts. why is that? is there a way to change the "zoom normal" default config?

this isn't new for anyone probably, but the hotas sync only works if the switch is on. for example, if I assign the tm warthog hotas EAC switch to the f18 anti skid switch (using a lua mod to make it work as a switch, not a toggle), and I start a mission with the EAC on the off position, the f18 will start with the anti skid switch set to ON regardless. the only case I noticed that the sync works is the opposite way, if I assign it to something that starts on off position by default (let's say the refuel probe which starts on retract position) if I assign the same EAC switch on my hotas to the probe, and I start the mission with EAC flipped to ARM, then mission will start with probe flipped to extend correctly. this is probably because of lazy programming, what I think is going on is that the hotas sync works by detecting switch input from the controller and if there's any input, then it will do something, such as turn the assigned commands to the same position, but if it doesn't detect any input, it does nothing, which is completely stupid since not everything on the plane starts on off, and if it did, then there wouldn't be a need for a hotas sync really, I could just flip everything off before starting a mission. this is terribly frustrating, specially considering that these modules and hardware isn't exactly cheap, and I spend the last 3 nights trying to setup my hotas for the f18. is there any way to make this work? I'm seriously considering opening my throttle and turning the switches upside down to match in game start position as if they were off.

Yeah I thought this would be the case. But spending two different controller inputs into just one single task seems like a waste. I realize that there are multiple actions when turning the lever to fold the wings, but ultimately it's just one task. guess I'll wait and see if there are any unused switches left after I assign everything I need

I see. so I assume there's no way to assign stuff like wing fold to a switch, since stow and turn (the wing fold lever) are different commands?

so I assigned the warthog hotas grip lift to the finger lift commands in dcs but it just lifts the handles, doesn't move the grip to off when i pull it back. am I doing something wrong?