jonsky7

Very disappointing!

1. snap view lines A10C DCS World/Mods/aircraft/A-10C/Input/A-10C/keyboard/Default.lua lines {combos = {{key = 'Num0', reformers = {'LWin'}}}, down = iCommandViewSnapView0, up = iCommandViewSnapViewStop, name = _('Snap View 0'), category = _('View Cockpit')}, {combos = {{key = 'Num1', reformers = {'LWin'}}}, down = iCommandViewSnapView1, up = iCommandViewSnapViewStop, name = _('Snap View 1'), category = _('View Cockpit')}, {combos = {{key = 'Num2', reformers = {'LWin'}}}, down = iCommandViewSnapView2, up = iCommandViewSnapViewStop, name = _('Snap View 2'), category = _('View Cockpit')}, {combos = {{key = 'Num3', reformers = {'LWin'}}}, down = iCommandViewSnapView3, up = iCommandViewSnapViewStop, name = _('Snap View 3'), category = _('View Cockpit')}, {combos = {{key = 'Num4', reformers = {'LWin'}}}, down = iCommandViewSnapView4, up = iCommandViewSnapViewStop, name = _('Snap View 4'), category = _('View Cockpit')}, {combos = {{key = 'Num5', reformers = {'LWin'}}}, down = iCommandViewSnapView5, up = iCommandViewSnapViewStop, name = _('Snap View 5'), category = _('View Cockpit')}, {combos = {{key = 'Num6', reformers = {'LWin'}}}, down = iCommandViewSnapView6, up = iCommandViewSnapViewStop, name = _('Snap View 6'), category = _('View Cockpit')}, {combos = {{key = 'Num7', reformers = {'LWin'}}}, down = iCommandViewSnapView7, up = iCommandViewSnapViewStop, name = _('Snap View 7'), category = _('View Cockpit')}, {combos = {{key = 'Num8', reformers = {'LWin'}}}, down = iCommandViewSnapView8, up = iCommandViewSnapViewStop, name = _('Snap View 8'), category = _('View Cockpit')}, {combos = {{key = 'Num9', reformers = {'LWin'}}}, down = iCommandViewSnapView9, up = iCommandViewSnapViewStop, name = _('Snap View 9'), category = _('View Cockpit')}, change to, or add {combos = {{key = 'Num0', reformers = {'LWin'}}}, down = iCommandViewSnapView0, name = _('Snap View 0 fixed'), category = _('View Cockpit')}, {combos = {{key = 'Num1', reformers = {'LWin'}}}, down = iCommandViewSnapView1, name = _('Snap View 1 fixed'), category = _('View Cockpit')}, {combos = {{key = 'Num2', reformers = {'LWin'}}}, down = iCommandViewSnapView2, name = _('Snap View 2 fixed'), category = _('View Cockpit')}, {combos = {{key = 'Num3', reformers = {'LWin'}}}, down = iCommandViewSnapView3, name = _('Snap View 3 fixed'), category = _('View Cockpit')}, {combos = {{key = 'Num4', reformers = {'LWin'}}}, down = iCommandViewSnapView4, name = _('Snap View 4 fixed'), category = _('View Cockpit')}, {combos = {{key = 'Num5', reformers = {'LWin'}}}, down = iCommandViewSnapView5, name = _('Snap View 5 fixed'), category = _('View Cockpit')}, {combos = {{key = 'Num6', reformers = {'LWin'}}}, down = iCommandViewSnapView6, name = _('Snap View 6 fixed'), category = _('View Cockpit')}, {combos = {{key = 'Num7', reformers = {'LWin'}}}, down = iCommandViewSnapView7, name = _('Snap View 7 fixed'), category = _('View Cockpit')}, {combos = {{key = 'Num8', reformers = {'LWin'}}}, down = iCommandViewSnapView8, name = _('Snap View 8 fixed'), category = _('View Cockpit')}, {combos = {{key = 'Num9', reformers = {'LWin'}}}, down = iCommandViewSnapView9, name = _('Snap View 9 fixed'), category = _('View Cockpit')}, (eg the "combos = {{key = 'Num7', reformers" is the programmed default key. When you change a keybind, a keybind differences file is created in your saved games folder. The default.lua file is not changed when you make changes, only the differences file. Any changes you make to the default.lua's will revert on the next update. That's where the mod I linked to earlier comes in. Or use a mod manager like OvGME.) ------------------------------------------------------------------------------------------------------------------------------------------------------------------- 2. No, not in DCS as far as I'm aware, the "toggle-ing" is a programmed function. eg, in the A10C iCommandPlaneGear - is the gear toggle command iCommandPlaneGearUp - is the gear up command iCommandPlaneGearDown - is the gear down dcommand The best you can do is have one function on button press, and another on button release This would be look back when button held, back to cockpit on release {down = iCommandViewRear, up = iCommandViewCockpit, name = _('F4 Rear view else cockpit view'), category = _('View')}, And again, if you want it to be keyboard or joystick, copy to both keyboard and joystick default.lua's

If you want to use a keyboard key, you must also copy that line into DCS World/Mods/aircraft/A-10C/Input/A-10C/keyboard Default.lua But there's no way to increase its speed I'm afraid, that is a function of the aircraft, not the keybinds.

It is possible with a .lua edit DCS World/Mods/aircraft/A-10C/Input/A-10C/joystick default.lua add this line (tested and working) {down = iCommandPlane_HOTAS_SpeedBrakeSwitchAft, up = iCommandPlane_HOTAS_SpeedBrakeSwitchForward, name = _('HOTAS Speed Brake Switch Aft- else forward'), category = _('HOTAS')}, you will see a new entry in your controls called HOTAS Speed Brake Switch Aft- else forward The original 2 lines are, the above just combines the two 248 - {down = iCommandPlane_HOTAS_SpeedBrakeSwitchAft, up = iCommandPlane_HOTAS_SpeedBrakeSwitchCenter, name = _('HOTAS Speed Brake Switch Aft'), category = _('HOTAS')}, 249 - {down = iCommandPlane_HOTAS_SpeedBrakeSwitchForward, up = iCommandPlane_HOTAS_SpeedBrakeSwitchCenter, name = _('HOTAS Speed Brake Switch Forward'), category = _('HOTAS')}, You may be interested in a really good mod for keybinds. Basically it saves modifications like this in your saved games folder, and adds them to the DCS keybinds file when the game loads. There's also a community keybinds project that adds hundreds of keybinds to all the different aircraft for switches and buttons that do not have a keybind by default. community keybinds https://github.com/Munkwolf/dcs-community-keybinds

Well you can still change the Arming Delay, but without the ground fuzing option you can't change post impact detonation delay. Arming Delay. Selects the delay between weapon release and arming. Options are 4, 4.5, 5, 5.5, 6, 6.5, 7, 7.5, 8, 8.5, 9, 9.5, 10, 14, 21, and 25 seconds.

But you could change it before today's patch, can't say with 100% certainty if actually did anything or not. and you could change the delay settings too.

Check out this post, be aware it doesn't work for FC3 planes

Unfortunately the RWR and IDS are not defined, and I don't believe they have been for any aircraft in DCS World, at least not the RWR. The added issue with any of the Flaming Cliffs aircraft is that their files are not modifiable like the full fidelity aircraft I'm afraid.

You can speed the process up somewhat. Place one tank, set the waypoint and hold condition. Copy that tank and paste as many times as you like, then just adjust waypoints. For trigger, make one trigger, clone it, only have to change the unit name.

Well that's a perfectly reasonable, well made explanation. I appreciate that you are open to the option.

If you're asking if there is anyway to have them scatter then I suppose there is, but it will take a bit of trigger setting. You could place several tanks as individuals, not a group. Give them all a waypoint in different directions, and set a hold condition to be stopped on a user flag. Then you could set a trigger for each unit, either if unit damaged or unit killed, then set user flag on. Then if one of the tanks gers hits, the user flagged is triggered, so the hold condition is removed, the tanks then carry on the set waypoint route. Not quite as simple as what you are asking but do-able. Example>>>>>>>>> scatter.miz

Have you opened up the controls indicator to see what your inputs are? Right CTRL + Enter IIRC Should only need around 1/4 right rudder for hover in ground effect.

I do use hot-start where possible, but in an online server you can't choose your weapons before you join the slot. So you have to do it anyway. Why doesn't it make any sense? What difference does it make to you or anyone else if I have my mavs auto boresighted? Like I said, if you want rivet counting realism then that's fine by me. Servers won't need anything new, they either force all the procedures or they don't. BTW I *never* align the INS my Harrier, and the INS doesn't drift because I use those options, even online. You'd best head over to RAZBAM now and complain about that!

Well different people want different things, that's what options are for. Nobody is asking for it to be removed, just a check box option in the specials tab to have it automatically aligned for a cold start, just as it is already aligned for a hot start. That way if you want the hyper realistic cold start up, then go for it. Those of us who aren't bothered about such things could check the box and not worry about it. I can't see how that would bother you?

Haha, I'm glad you found the humour in that... I didn't mind doing it as long as it worked. Before this current patch you just had to go through the motions and it would be locked in. Then someone complained that wasn't realistic enough, because the couldn't get it to not align properly even when locked the TGP and MAV to two different targets. Who cares? Why anyone would want it to not be aligned is beyond me. Anywho, they tried to fix that error, and now introduced another whereby it doesn't seem to want ever to be aligned. Or it's aligned but at one distance only, do the boresight at 5nm, well then you're going to have to target everything at 5nm if you want to use the TPOD. That's a reported bug btw.

I did see a warning in the manual about these heavy cards and PCIE slots. I'd definitely be trying to RMA it if I was you if it is new enough. I think I also noticed that only the top slot is PCIx16, and the 2nd is PCIx8. I may be wrong about this. Not sure if the bandwidth will be limited at 8x anyway.

I'd be happy with an option to remove JHMCS alignment as well, thanks for suggesting it. Chad is only asking for an OPTION to remove it. Not that it is removed.

Rel4y from the post below sold me a Hall effect potentiometer for the friction slider and it works. However, it did not fix the jitter in that axis. I saw another post somewhere that mentioned a powered USB, and that did fix the jitter. A combination of powered USB and hall effect sensor is spot on mind you. I paid 7eur shipped, but that might not be an official price. I haven't really seen Relay mention the warthog in his post other than my request, so I'm not sure if he planned on selling them in the end. I think I may have been the first to enquire about them. But he has all the details now. Wouldn't hurt to ask

Got the latest BIOS installed for the motherboard? https://www.msi.com/Motherboard/MEG-X570S-ACE-MAX/support#bios

With the 7900 plugged in does the computer still boot up? Can you get into the BIOS with that card plugged in, or is the screen always blank? If it's always blank, does the motherboard show a code on it's little LCD display? Which monitor are you using?

Yes please for the option

And just to make it clear, long means a long keypress, or press and hold for more than 1 second IIRC

Well in this picture the LEFT MFCD is definitely NOT SOI, it even says it in the white text box at the lower end of the screen. When the Left MFCD is SOI, that white box with NOT SOI in it will disappear. it is saying this display IS NOT the SENSOR OF INTEREST. I would assume in this picture the HUD is SOI.

Two things you can try to solve/minimise the jitter, the first is free, and that is to either use the software to disable the backlighting LEDs, or turn them up to full, anything else seems to increase the jitter. The second is to use a powered USB hub, not too expensive. I even had a custom HALL effect sensor made for the "zoom" slider but it didn't fix it. A powered USB hub did though. Which I learned from somebody else with the same problem. I had the same issue whereby it didn't seem to be saving my preferred FOV when I saved a new snap view. What you can do is set a User Curve for the Zoom slider. If you adjust the centre "button" you'll see that the FOV changes when the slider is in the detent, put that where you want it. When you first get in a new plane, the FOV may be the default, just wiggle the slider out of the detent and back again. Then I did a bit of maths to figure out what the other buttons should be. eg my centre is 30 from centre to either end is 5 steps, 30/5=6, so each step up to the middle is increased by 6, (0 6 12 18 24) 70/5 = 14, so each step from the middle to the right increases by 14, (44 58 72 86 100) Downside is that you need to do this for each aircraft, but it's saved in your keybindings, so you should really only have to do it once. This gives a linear change in either increasing or decreasing FOV from the centre, obviously different in each direction from centre but it's not noticeable.

I think this happens when all 3 of your monitors are not the same resolution. I haven't done a lot of testing to be honest as I don't have 3 monitors to set up like this. Does it still do it if you use Nvidia surround or AMD Eyefinity to make 3 monitors act as one monitor?