LG-Skyman
Members-
Posts
75 -
Joined
-
Last visited
About LG-Skyman
- Birthday 01/01/1988
Personal Information
-
Flight Simulators
DCS, Il2 clod, RoF, il2 Bos
-
Location
Poland
-
Interests
Gliding, Motorcycling, History
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
-
Cargo plane deploys troops, vehicles and equipment without LUA
LG-Skyman replied to chnapo's topic in Mission Editor
The game already has supply mechanic and option to limit weapon availability, but I'm not familiar with it. You may then use the cargo plane just as an eye candy/mock. Wysłane z mojego MI MAX 3 przy użyciu Tapatalka -
Need help repairing mission-DSMS empty, then no SPI
LG-Skyman replied to RepoManR6's topic in Mission Editor
Does it happen after rearm or right in the beginning on the ramp? Wysłane z mojego MI MAX 3 przy użyciu Tapatalka -
Make messages to appear each time an attack group or unit function is called in all your scripts: your own, skynet, moose and mist. In the content put an information what units are involved and which function is it. You can of course trigger it only when both units are red. This should allow you to trace the cause hopefully. Fortunately you can read and modify all these scripts. There's a Roe setting in Me, but I don't know, if it allows for friendly fire. This may be just a bug in one script or they conflict with each other in some way. Good luck. Wysłane z mojego MI MAX 3 przy użyciu Tapatalka
-
If anywhere, I'd place it in the map ruler. We'll be able to see it at will anywhere. A separate input field would be an unnecessary complication, but you may also add a read only label showing either near an input heading field -- similar thing to IAS, TAS and GS information. This feature may be useful for most hardcore mil-sim guys, to me such errors/deviations are insignificant. I can calculate them myself or take them into account, when needed. Wysłane z mojego MI MAX 3 przy użyciu Tapatalka
-
Script wanted: more realistic artillery effects on SAM units?
LG-Skyman replied to IAF.AssafB's topic in Mission Editor
There are various target range scripts: they tell how close your bomb fell, for example. You can use parts of their functionality. This should be a good starting direction. I used Moose for instance. You can also check out sead scripts, they turn off sam's radar, when targeted by harms. Wysłane z mojego MI MAX 3 przy użyciu Tapatalka -
Moose has that exact functionality: https://flightcontrol-master.github.io/MOOSE_DOCS/Documentation/Ops.RecoveryTanker.html Some other frameworks may also support this, sorry, I know only this particular one. Wysłane z mojego MI MAX 3 przy użyciu Tapatalka
-
Triggers and zones in background? How it works?
LG-Skyman replied to RoGaR's topic in Mission Editor
Certainly other colleagues know more and I can only point you a general direction, but I don't want to keep you waiting. My guess on the no script call examples is, that they maybe are done using ED's support or effectively encrypted. If you need help making your first script, then I'd propose Moose framework, which enchances DCS API objects and has vast functionality. There are of course others, but I know this one somewhat well. Starter's guide: https://flightcontrol-master.github.io/MOOSE_DOCS/ The issues and my experiences: * I haven't got eclipse LDT to work, so I use notepad++ with syntax highlighting * I use MESSAGE class to print debug information and main DCS log to check errors * Script runs until a first error * My only triggers are: load moose.lua script and then load my custom logic script * The december 2021 release had moose_.lua (smaller size, no comments) file somewhat broken, so I use the full moose.lua * I simulate triggers by running a SCHEDULER instance to check conditions (unit in zone in my case) every 1 second (the smallest interval allowed). You may need more scheduler tasks to keep logic tidy and clean as it may get complicated * Moose possibly already have the functionality you need to make * Documentation on github is newer than the release you got, but the bigger moose.lua incorporates good commentary and examples in the form of actual code * You can use every single moose class separately to achieve more granularity I can answer your question, if I get the notification. Good luck Wysłane z mojego MI MAX 3 przy użyciu Tapatalka * moose detects on startup zones, triggers and some dcs objects for you to access in its database Wysłane z mojego MI MAX 3 przy użyciu Tapatalka -
Random Aircraft Patrol spawn for a persistent online mission
LG-Skyman replied to Tank50us's topic in Mission Editor
Moos has a few plugins that may suite you: 1. Cap plus gci: https://flightcontrol-master.github.io/MOOSE_DOCS/Documentation/AI.AI_A2A_Dispatcher.html 2. Cap in zone: https://flightcontrol-master.github.io/MOOSE_DOCS/Documentation/AI.AI_Cap.html 3. Just patrolling: https://flightcontrol-master.github.io/MOOSE_DOCS/Documentation/AI.AI_Patrol.html I think the latter two rely on an event to start operations, but I hope you can use your own triggers for that. I have used other moose scripts before and I can recommend them. It was long time ago, so I may not be the one to answer your technical questions. Wysłane z mojego MI MAX 3 przy użyciu Tapatalka -
Have you considered ctld framework? I'm not sure, if it will suit you. Wysłane z mojego MI MAX 3 przy użyciu Tapatalka
-
+1 Wysłane z mojego MI MAX 3 przy użyciu Tapatalka
-
There is a way to start a mission as if it was MP: set the controllable aircrafts to client instead of player. I hope, I remember it right. Wysłane z mojego MI MAX 3 przy użyciu Tapatalka
-
+1 Wysłane z mojego MI MAX 3 przy użyciu Tapatalka
-
Depends on the setting, default setting is to pump from internal fuel tanks only, if I remember correctly. The light indicates either empty or not present drop tanks. Please refer to the most convinient manual. Wysłane z mojego MI MAX 3 przy użyciu Tapatalka