-
Posts
2070 -
Joined
-
Last visited
-
Days Won
3
Content Type
Profiles
Forums
Events
Everything posted by FlightControl
-
I've created today a "Moose for Dummies" tutorial series, which is something I wanted to do already for a very long time, but never got to. There are now about 15 videos. The series explain you some stuff on how to apply the mission editor and lua scripting using the MOOSE framework. For those who don't have lua knowledge, I've created some basic overviews on the lua language, to set some basis to find your way. This video tutorial series is going further as we speak... Suggest you consult the following playlist: Wherein this is the first video: ZqvdUFhKX4o Enjoy and I hope for many this puts the bridge between Mission Editing and Scripting. FC
-
I "think" I have a workaround for this problem. When you edit the initial speed of the airplane (so at node 0), and put a high value, I have observed the planes to fly faster.
-
It is about testing this is a multi player environment, with dynamic A2G tasking. If you wanna join, please tell my what machine you would like to fly, and your name on skype. (in a private message to me). We're going to do a test on the NTTR, because DCS 1.5.7 is unplayable in MP.
-
Guys, I don't know if anybody would have time to help me with some testing of the dynamic tasking engine? It needs some more testing. I have a simple but fun test mission here. It concerns dynamic tasking and is something you've not have flown yet. If you would have time, could you let me know? We'll setup a conference call using skype. Skype is my preference because i can also share screens and people from multiple squadrons can join. FC
-
Guys, this is really really very bad, this error. And i am afraid that this error is deep within the current engine logic of 1.5.7, somewhere hidden. It takes ED way too long to fix this. The performance drop in 1.5.7 is significant comparing with 1.5.6. Run the attached mission... It is a simple test. 2 planes fly towards Sochi. They will be intercepted by 2 SU-27. Speed up the time lapse to around 10 acceleration, using LEFT-CTRL-Z (or W for azerty keyboards). As soon as the interception planes spawn in (the Su-27) the performance will just drop immediately... Now run the same mission on 1.5.6.... Accelerate to 20... As soon as the interception planes spawn in (the Su-27) the performance is still okay... When the planes leave Sochi, it is even better, and you can accelerate to 100!!!! Is there any more information on this error please? This is destroying the game. Is there a beta coming out some time? AID-009 - AI_A2A - Border Test.miz AID-009 - AI_A2A - Border Test.lua
-
MOOSE 2.2.0.pre updates New updates have been released in 2.2.0.pre: Changed methods :New() and :NewWithBorder() for the AI_A2A_GCICAP module. A resources parameter has been added. By default, when Squadrons are defined using AI_A2A_DISPATCHER and AI_A2A_GCICAP the Squadron will have unlimited resources, unless the now optional Resources parameter of the :SetSquadron() method is specified. Added methods :SetSquadronTakeoffInAirAltitude() and :SetSquadronTakeoffInAirAltitude() in AI_A2A_DISPATCHER and AI_A2A_GCICAP. Modified method :SetSquadronTakeoffInAir() in AI_A2A_DISPATCHER and AI_A2A_GCICAP, adding an optional TakeoffAltitude parameter. Modified method :SpawnFromAirbase() in SPAWN, adding an optional TakeoffAltitude parameter. Please check the new methods added to set default altitude and the resources. There is an important change in the system. the :SetSquadron method has now the Resources parameter made optionally. When not specified, your squadron will have unlimited resources. When using GCICAP, the :New and :NewWithBorder constructor methods now have an additional parameter Resources added, which can optionally be given to set the resources of each squadron created. If not specified each squadron will have unlimited resources. Check the documentation on the :New constructor of GCICAP. and the :NewWithBorder constructor of GCICAP. You can download the latest release from: https://github.com/FlightControl-Master/MOOSE/releases FC
-
So checked your mission, and it works fine. A CAP spawns between 180 and 600 seconds. You can speed up the time elapse using L-CTRL-W (or Z). Small thing: I changed a bit the test.lua to this: GCI_Red = AI_A2A_GCICAP:New( "EWR", "TEST", "CAP", 2 ) GCI_Red.SetSquadronTakeoffInAir() GCI_Red.SetSquadronLandingNearAirbase()CGI_Red is your GCICAP object, and from this object you use its methods. Also in the mission editor, you can set both triggers at "MISSION START". No time delays are necessary at the triggers. Enjoy! test.lua test.miz
-
Checking...
-
OK I will take a look. Is it Caucaus, NTTR or Normandy?
-
Yes, that is done on purpose for the testing. First of all, did you have a read on this documentation here? http://flightcontrol-master.github.io/MOOSE/Documentation/AI_A2A_Dispatcher.html#AI_A2A_DISPATCHER I will help you with the process, but want to be efficient and see how i can best help you. Please first have a good read through the documentation. It will put the subject well in your head and then we can discuss efficiently. Otherwise i need to explain for zero, and that would not be efficient. Thanks for using. I have time today to help you out. FC
-
Please register your enhancement requests, ideas, and issue on github here: https://github.com/FlightControl-Master/MOOSE/issues I get from many sources many requests, ideas, and issues through various channels. The above issue list allows you to register these items per subject. Please do so, as it will help me and my memory to remember and do something about these issues. We can discuss there, everything is traced, I can share content more easy and it makes just a better place to discuss and follow-up on these items! Note that it is perfectly okay to discuss here, no issue, but just don't forget after we've come to a conclusion to register your request on github! You can then cut/paste some of the text that we wrote here also in the issue log. In this way you contribute a lot to the project! Thanks all! FC
-
Where are the times... You would buy a sim and get a booklet with it... Including printed maps etc. These times are gone now. I did upload pdf files on my A4 sized ereader. DCS manuals look great on ereaders. 47 here... Been using flight simulations for a long time. I think that the 40-ers and 50-ers come from a different generation where each year, as the hardware for home PCs improved, new flight simulations appeared with great new features. In our search for the ultimate sim... DCS world is coming closer to that ...
-
SCORING in moose. However, I have built in a logic to score the hits, but once a hit has been detected, all sequent hits within a fraction of a second don't count. But if a target hasn't been hit for about half a second, then sequent hits are scored again. The reason why it was built this way is to avoid a gun hitting a ground target where each shell hitting the target would count a point. F.e. The ka-50 can load the rapid fire pods, which fire hundreds of shells in a second. This would generate hundreds of hit points and is unrealistic.
-
That is what the MOOSE framework is about. These is a learning curve, but there is a big reward and learning it is kind of fun too! You do things you thought were never possible. I've seen missions made with hundreds of triggers using the ME. Which were rewritten using moose in... 10 lines of code... Using the SSE would take much longer though. Let us not deviate from the subject. Could it be language barriers? Culture? Other social media standards? Fear? The unknown? You don't like the Galliae? What about Russia? Asia?
-
I know. It is a challenge to get the world focused. I have "some" Russian skills, but i would make a fool of myself if I would join the Russian forums. My Hungarian, French, German, English and Dutch is more fluent than my Russian. So, is there somebody who could help out?
-
Where is Europe and the rest of the world? This is another interesting picture. A view of the MOOSE videos. This shows how many videos are watched per country. I wonder... Are there only DCS players in the USA? Not that people don't watch from Europe and Australia, but it seems that there is much less activity. And what about Afrika and Asia??? What about Russia? Interesting. Come on guys in the world, don't miss out on this :-) https://www.youtube.com/channel/UCjrA9j5LQoWsG4SpS8i79Qg/playlists?sort=dd&shelf_id=0&view=1 http://flightcontrol-master.github.io/MOOSE/ FC
-
CAP and Refuelling All, A new capability has been added in the AI_A2A_DISPATCHER and AI_A2A_GCICAP. This is CAP and Refuelling to an airborne tanker. Have a look at this video here. 6iQ7ImvG-DQ The video explains what CAP and Refuelling is all about. It then demonstrates a working mission and the CAP and refuelling in action. Then it explains how to use and setup the CAP and refuelling in your scripting, using the DISPATCHER or GCICAP module. The idea was born from a requirement set by Sierra99 on this forum, and Neck from 132nd team. - Sierra99 - NECK The MOOSE Release 2.2.0.pre has been updated, please download the new Moose.lua from here: https://github.com/FlightControl-Master/MOOSE/releases It also contains a couple of other optimizations: Implemented a working Stop time on SCHEDULER. Implemented the CAP and Refuelling capability in the AI_A2A_DISPATCHER and AI_A2A_GCICAP. Methods :SetDefaultFuelThreshold(), :SetSquadronFuelThreshold(), :SetDefaultTanker(), :SetSquadronTanker() have been added in AI_A2A_DISPATCHER. The new capabilities are documented here: http://flightcontrol-master.github.i...ispatcher.html The demonstration mission can be found here: https://github.com/FlightControl-Mas...0Tanker%20Test Have fun! FC
-
CAP and Refuelling All, A new capability has been added in the AI_A2A_DISPATCHER and AI_A2A_GCICAP. This is CAP and Refuelling to an airborne tanker. Have a look at this video here. 6iQ7ImvG-DQ The video explains what CAP and Refuelling is all about. It then demonstrates a working mission and the CAP and refuelling in action. Then it explains how to use and setup the CAP and refuelling in your scripting, using the DISPATCHER or GCICAP module. The idea was born from a requirement set by Sierra99 on this forum, and Neck from 132nd team. - Sierra99 - NECK The MOOSE Release 2.2.0.pre has been updated, please download the new Moose.lua from here: https://github.com/FlightControl-Master/MOOSE/releases It also contains a couple of other optimizations: Implemented a working Stop time on SCHEDULER. Implemented the CAP and Refuelling capability in the AI_A2A_DISPATCHER and AI_A2A_GCICAP. Methods :SetDefaultFuelThreshold(), :SetSquadronFuelThreshold(), :SetDefaultTanker(), :SetSquadronTanker() have been added in AI_A2A_DISPATCHER. The new capabilities are documented here: http://flightcontrol-master.github.io/MOOSE/Documentation/AI_A2A_Dispatcher.html The demonstration mission can be found here: https://github.com/FlightControl-Master/MOOSE_MISSIONS/tree/release-2-2-pre/AID%20-%20AI%20Dispatching/AID-016%20-%20AI_A2A%20-%20Refuel%20Tanker%20Test Have fun! FC