Amarok_73

Yes, this gonna work. In meanwhile I've eventually come to the similar in the script as below. Future seems brighter then. :-) pipok = {} function pipok.respawnGroup() for key, value in pairs(mist.DBs.groupsByName) do trigger.action.outText(string.format("%s", key), 2) end mist.scheduleFunction(pipok.respawnGroup, nil, timer.getTime() + 10) end trigger.action.outText("Executing RespawnPrefix script 17",10) pipok.respawnGroup() Thank You for Your effort, Steggles.

Then what I do wrong with below? I've lost 3 hours of evening so far to find why this returns zero, and I am now totaly out of ideas... pipok = {} function pipok.respawnGroup() local GroupList = mist.DBs.unitsByName trigger.action.outText('#GroupList: ' .. string.format("%i", #GroupList), 5) for i=1, #GroupList do trigger.action.outText(GroupList[i]:getName(),5) end mist.scheduleFunction(pipok.respawnGroup, nil, timer.getTime() + 10) end trigger.action.outText("Executing RespawnPrefix script 8",10) pipok.respawnGroup() The same effect is if in place of "mist.DBs.aliveUnits" I'll use "mist.DBs.groupsByName", and only message I am repetitively receiving is "#GroupList: 0".

Steggles, I couldn't wish more adequate person to get into my humble person's troubles. :-) Thank You for that answer - for sure I'll work out based on that, what I want in this specific case. Just one more question - what is the hash sign loops I've noticed in some scripts? Isn't it the method to define number of elements in table that have to be traversed by loop?

Then here comes another one (pretty obvious for expected learning path): how to iterate through all groups and execute this script on groups that's name contains specific string?

Hello, Since I still feel pretty lame in Lua scripting, I'd like to ask other - more knowlegeable colleagues if this simple script executed after MIST initialization should in effect cause that group "Agressors" will be checked for being alive every 30 seconds, and if not, then will be respawned? EDIT: After some testing, and tweaking the script, now it is what at least seems not to cause any errors. But still I am not sure if this should provide expected effect. pipok = {} function pipok.respawnGroup(groupName) if not Group.getByName(groupName) then mist.respawnGroup(groupName, true) end mist.scheduleFunction(pipok.respawnGroup, {groupName}, timer.getTime() + 30) end pipok.respawnGroup('Agressors') EDIT2: Well, it works. :-)

Install Horse of War cockpit mod, then You should be able to see sharp labels at least in medium texture settings. EDIT: Sorry Mike_Busutil, didn't noticed Your post.

Thank You Ian. I'll give-up with this then until it will be possible to do easier way. :-)

Hello, Does anyone know if this is possible to send message to A-10 (SMS display) using script?

I am using gray cockpit, and everything works properly after update. The only issue is related somehow to radio. When I start my own training mission, where I am on final approach, and contact tower, there's no sound and no text response from tower. But if I'll eject and respawn with Shift+Ctrl+Tab, radio communication gets back to normal.

I have executed repair, then tried to load these missiles again, and effect is the same. Weird is, that sometimes it happens just after first pylon is loaded, and sometimes it seems, that the error occurs just before confirmation of loadout from ground crew have to happen. Is it possible to determine strictly what is broken and try to repair only this part? EDIT: Small update - after module reinstallation, this problem isn't occuring. Additionally, few sounds have appeared (like brake pressure decompression), and force feedback started to work correctly.

Hello, As in post title I've described - whether I'll try to load R3R-13 APU MI standing on apron, or preload this weapon by selecting it in mission editor, there error appears, saying that Avionics.dll module caused error in DCS.exe. Logs and mission file in attachments. Best regards. Avionics_dll_error.zip randomairtraffic_scripttest.miz

Since for some reason I can't play replay whole track (it's just hanging at the third startup) I can't really say if this is help in this specific situation, but for sure I'll keep in mind where to look when next time this will happen to me :-) Thank You anyway.

Ah, so it was hidden behind throttle, and that's why I couldn't notice any movement in cockpit when I used rAlt-H/rCtrl+rAlt+H.

Hello, It occured yesterday, when I was flying on our squadron multiplayer server. In the third flight after I've crash-landed, respawned and airborned, I've noticed that there's no ailerons, so I could only change pitch, and turn using rudder. After that flight, I've found in keyboard mapping, that there's something like aileron boosters, that disabled can have such effect. So I've watched replay to find out what switch I could use by mistake, that affected these boosters, but I was unable to find out such switch, and all others I know seemed to be in correct setup. So I really don't know if indeed it was disabled boosters or it was system malfunction, or perhaps bug. If it can help, here's track. Since it's 15 Mb large, i can't upload it in post, so I've put it on google drive. EDIT: The third flight starts around 117/13:20 mission time.

This 'rotaton' of forces can be caused by the same reason like long time ago it was in KA-50. That time it was required to do some manual configuration editing, to correct situation.

Yes, my G940 is working properly in other products. And regarding update, I am not sure what version, and since I am now at work I can't really verify it, but I've done this udpate yesterday, so I assume it's recent offficial update. Maybe let's try different approach - what behaviour should I expect from my FFB? When and how it should work in Mig-21B? EDIT: The version I have is 1.2.10.32275.

G940. :( EDIT: After restart of computer and second restart of game (counting from moment of update) I can see difference. There's shaking that probably is meant to come from engine - seems to be more or less proportional to the RPM - and that's all. Like Zaelu said, no feedback from steering planes, and even no effect related to trim setting. It's just very soft and barely keept centered. Far from what A-10C have implemented. So it seems, that in my case, shaking have to be disabled, because feeling the engine just working is pointless, and works on me as distractor instead of giving any feedback.

Well, does this fix for FFB been already published with recent patch? I can see change, but now it's worse than before, since vibration of joystick is permanent, whatever I'll set in ffb options in axis mapping, and even SimFFB now can't take over control of the ffb, so with this program running, joystick is vibrating anyway. The only option now is just to unplug power from controller.

Pretty decent movie. :-)

I have been flying KA since almost beginning, as well as Huey, I find UH easy to fly in either FM (especially 1.2.5 was good to do "TIE fighter tricks"), but still KA is my choice when it comes to survivability and usefullness on the battlefield. Especially when hunting in packs. In UH, all the pilot have to do is to pick-up, deliver and return in one piece... more or less, so it's natural, that this machine seems to be "underinvested" comparing to KA. Anyway, when it comes to go into the battlefield for adrenaline, i enjoy UH, but if I have to be "agile, mobile, hostile", KA is so far the only choice I can do.

You could use this font for it: http://www.dafont.com/october-guard.font Good job though!

It does have drop down menu to select joystick button.

Ok, I've had to delete my current mapping files, and remap everything from scratch, but now I have all needed options (I hope). On the other hand, shouldn't radar altimeter sound audible warnings, when altitude is out of set min and max values?

To add something to list of issues after 1.2.6. was applied, the axis assigned to throttle is not working now. Other issues are as above: broken miniguns sound, much more collective required to pick-up the bird, no possiblity to lower pilot's targeting hardware. And it's just me, or it is more common, that low RPM warning is not audible even if switch is set to enable this feature?

It's only me, or this reticle can't be synchronised with gun's aiming point when it's moved using Sight Down/Up/Left/Right?