void68

Well, I have no real additional code here, I did an "execute script file" mist.lua and "execute script" with the code under triggers action. Gruppe (ground unit group to spawn) and Zone (triggerzone) were both defined. I don't quite understand as Isn't that exactly what I wrote and what it should be: mist.respawnInZone('Gruppe','Zone')? Gruppe and Zone are valid. I even put a space at the approbiate places around the comma like in the wiki, no change. Even stranger thing is that after I copied/pasted the different codes from the wiki it suddenly worked - despite they look exactly like my input - the parameters between {} and the nil, 4000 weren't the problem as I deleted them and still the script works. SA2 is the name of both the group and the zone, not the best choice I know, but it was just for testing purpose. Well, I don't know why it does work now and did not before. Thanks for help nontheless.

I used mist.respawnInZone('Gruppe','Zone') and it comes up with with error. What am I doing wrong?

thanks guys, lots of help to prevent future issues

Thanks, I always planned to use the Command Injector but was too lazy. I didn't mention my editing first because I thought that adding a few lines in the .lua (like I did hundreds of times before - and I still wonder what might have gone wrong) could have broken the commands, but not that the devices were put to sort of offline. I will walk through Quaggles' Command Injector then. Still I wonder what will happen if DCS adds some required new code to the default.lua that the backup does not have. That's why I went from just replacing to editing / adding lines to it.

Thanks so far. What helped: After a DCS repair I got my default.lua back and it worked. Before I had copied my individual .lua entries back into the default.lua from the after-update DCS-backuped default.lua like I have to do after each update, these additions enable keybindings for ejection arm lever, pneu/elec elevation and different speed settings for CRS and HDG knobs on the HSI (again thanks to @LeCuvier for helping me with these two years ago). Perhaps something went wrong with the copy+paste, despite I went on with extreme caution and my experience is over two years... when I tried it 2nd time it worked again. DCS doing DCS things... or I had a bad moment. Ah, damn, right... there they are. Thanks for pointing me to them. They are intact I just hadn't noticed them there. I was in real stress as I lost my config 1h before a big MP game. Well, 99% is working again.

I reinstalled the default.lua and at least they respond again. Don't know why, after another edit it still works. Now my default settings like MFDs are empty. They had a default binding before (MFD button #1 on #1 etc) and I didn't save them - as they were installed after joystick / MFD installation. DCS put some default over it, like on the HOTAS switches. They are all gone. How to get the default back?

All controllers are "dark", they lost all keybindings and I can't neither load my profiles nor set new keybindings. They are just "dead". Other models work, it's just the F-16. Did a DCS repair, no change. Did restarts, reboots, the usual stuff. How to get my devices work in the F-16 again.

I can't login and have to play offline - that happened the last 2 weeks occasionally. New is "you have to enter a local password" and it says it does not match (wrong, it's the same) and don't even let me access any module. Can we have an urgent fix? What's going on since last patch? edit: did a DCS-repair, did a reboot, changed my password just to be safe: no change! No login, no access to neither modules (just the standard free ones). edit2: added this to \Windows\System32\drivers\etc\hosts now it works. 185.195.197.4 api.digitalcombatsimulator.com

Thanks to you both. My cockpit is already cramped as I put it onto a motion rig and everything has to be fixed, so no mouse, just a trackball (bolted down to an alu extrusion) on the right. Almost impossible to mount something between my legs neither on the left side (left F-16 console is packed with needed switches). Well, it might be a workaround for others, I just still wonder why no one else wants mouse movement possibility on the HOTAS with all these possibilities. I recall from my memory that mouse emulation by stick was possible even with the old 1. gen Cougar HOTAS in the 2000's. But Quaggles might be a good idea, whereas I don't like to start just another background program for a simple task DCS could solve with a minimum of corrected coding (already need a handful for DCS: rig program, 2x immersive progs for bassshakers, motion compensation, VR prog, joystick progs). Perhaps it even helps with this ridiculous 3xCTL E for ejections...

Ich empfehle Dir weg vom HF-8 hin zum Bassshaker. Den HF-8 hatte ich auch vor meinem Rig zur (bescheidenen) Simulation von Kräften / Beschleunigungen neben der reinen Vibration. Die benötigst Du aber nicht mehr im Motionrig. Ist nett, aber es fehlt wirklich der Wumms. Gerade im Heli ist das Flopflopflop des Shakers unglaublich beeindruckend und verstärkt das leichte Hüpfen des Rigs. Lautsprecher und Verstärker gibts für je 80€, Software für 30€. Buttkicker ist unnötig und überteuert. Die Rennheinis packen sich 4-5 Shaker mit 5.1 ins Gestell...

Danke schön . As I fly in VR I don't need the camera movement to look around. When I switch to any outboard view I can look around in that outer view, but I can't change its position. I can't rotate around an aircraft with any other device than the mouse, I just can look around from that initial position. So with HOTAS idea in mind it's very annoying to get the hand off the stick and grab the mouse when I got enought analoge hats/sticks on my HOTAS. I wonder why none of the devs reply with a solution. What's the idea behind limiting camera movement just to the mouse?

This is a General setting but can as well be found in all individual planes' axis setting, but I just checked for the FW-190 D-9, the F-16, the A-10 and F-4. Increased contrast dramatically for better visual difference what fields are "on" and "off"

Wake turbulunce is no factor when in pre-contact or when on the boom or way ahead below the belly. Curve parameters seem ok. Refueling experiece however varies a lot depending on weight and drag of your aircraft, asymmetric loadout, speed and altitude of the tanker, lighting conditions and pilot's endurance. Sometimes it helps, especilly when CAT I, to deploy the brakes a bit. Just a guess and from my experience as it indeed helps me: Keeping forward / aft stability is more difficult than up / down in my case as going up down can be achieved instantly. You always see an arrow up or down and know where you are or where you have to steer. Forward / aft is just helpful as long as you see a relation to a fixed mark. You really can see the "off" indicators due to the high contrast. It seems the "off" indicators are more important like in this example: you got from aft to front 1 off, 1 lit (with bad contrast), 3 off and you know exactly where you are and where you have to go. In an overall low contrast situation you just see one lit indicator and have to evaluate just by its position where you are.

Let go of all hope, they will never change that. I wait for a change in ejection button behaviour from three needed keypresses to just one keypress (for homepits) for 3 years. Sidenote: I feel very comfortable with the faint morse code while on ILS, helps me relaxing.

First try with level, straight formation flying. Your wingleader should be in autopilot and speed should already be settled. Identical loadout and Fuel Flow declaration can be helpful. Every change in speed, altitude, heading should be gentle and should be declared. That's what the winglead can do. Once you are settled stay with minimum inputs, you can even try with autopilot to keep the same altitude or pitch (yes, that's a sacrilege I know, but that's one axis less to care for). With the Paddle on your HOTAS you can easily adjust the altitude to aim for. Most of the time you have to adjust throttle inputs, a bit forth, a bit back till you find the sweet spot. Brakes help for quick change. Think ahead of your engine, it got quite some latency (other than piston engines). First get rid of your overshooting. Better take some time and learn about closure rates and how they correspond with the screen, i.e. how fast the "target" aircraft grows on your screen. Do you use VR? Headtracking? Keep your eyes somewhat fixed on your lead, but also keep him more in a peripheral view area. Like AAR and when you are dashing your car through a very narrow lane or right next a truck while in a narrow roadwork: If you fix your eyes on the side you will oscillate your inputs. Just look ahead and subconsciously you will steer correctly. Again, short, quick inputs, else it leads to PIO. Try different formations with that more or less stable lead aircraft.