-
Posts
65 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by Naj-Treg
-
Hello missionbuilders. I have a question regarding spawning airplanes in multiplayer. current problem: If i set a planegroup with 1 or more AI wingman, your AI wingman keep flying the mission when you die..... If the player re-spawns the 'old' AI wingman are still in the air and the player does not have his wingman to control. Is it possible in MOOSE to 'bind' the AI wingman to some kind of status of the player? for example...when player dies the AI de-spawn or 'die' too. Then when hit re-fly the player starts with his wingman. If possible. Can someone guide me in the right direction. Ps. i have MOOSE setup in ldt as shown in the youtube tutorials. with kind regards, Naj-Treg
-
Hi all. I have a question/problem with a mission i created. I created a WWII intercept mission where players and AI work together as interceptors. I have a working GCICAP script. I setup A2ADispatcher:SetSquadronOverhead and A2ADispatcher:SetSquadronGrouping so that there is not a 1 on 1 but lesser GCI plane spawn. This way the human players can fill the gap. This script works great. Now for the problem. When the enemy bombers are in range, the script spawns the GCI planes and they take off. After take off all the GCI planes go after 1 enemy plane till it gets shot down. Wich results that the rest of the bombers follow the route without getting intercepted only till the first plane get shot down. then it all repeats for the second plane. Am i doing something wrong? or is this a flaw within DCS/Moose? I tought that the spawned GCI planes would go after different targets and not all after one target. Is there a solution for this? Greetings Naj-Treg
-
Hi SUNTAG. Sorry for my late reply. Could not reply faster....very busy @ work. For some reason i can't find the link to the BF-110 mod anymore :( I report here if i can find it. Keep up the good work!:thumbup: Naj-Treg
-
I also have a question. I have the script running great. and many thanks for the template of the chains! The only problem i have is.... the radar does not see some of my mod planes. for example the mod BF-110. I added the planes in the chainhome.lua file. but radar does not see it. If i change the flight to HE-111 (mod) then radar will see it. is there something am missing or doing wrong? Greetings Naj-Treg
-
Yes this is possible. Open the chainhome.lua file. and change the line 'ewrs.messageDisplayTime = 25 --How long EWRS BRA messages will show for (seconds) ' Change number 25 (seconds) to the disired seconds you would like. it is also possible to change the time in between you get a radar update. to do this change the line ' ewrs.messageUpdateInterval = 60 --How often EWRS will update automated BRA messages (seconds) ' Change number 60 (seconds) to the disired seconds you would like. Save the file and reload the chainhome.lua again in the mission thru the trigger menu. If you dont reload it in the mission the saved options wont work in the mission. Good luck!
-
I did a google search on 'Mofiki's Coordinate Finder' and got a download link on the first hit it gave. should not be too hard to find :thumbup:
-
For me version 2.5.0.15184.338 get the panel working.
-
No problem. I really appreciate all those mod makers and the time and effort they put in the mods to make this sim better. As you said...you can't please everyone. Keep up the great work:thumbup: Naj-Treg
-
Thanks learned something today:thumbup:
-
Glad i could help you. I know the struggle with the resiolution setting.... at first i ran my panel on a 1024x768 monitor. The software does scale the panel size but not the image and gauges. My work around for this was: - setting up my panel on a screen with a 1920x1080 reselution. -under configuration tab select editor mode and click show cockpit. -go to instruments tab. If correct all the gauges have a orange highlight. when you click on a gauge it wil be highlighted in orange. enter a smaller number for size px. click in your panel the same gauge again. now it should get smaller. do this for every gauge. after all gauges are smaller, drag them all to the left side of the panel. best is to make or 3 rows (depends on how small you make the gauges). now save your profile. At this point go to the configuration tab and change your X and Y resolution to the desired screen and place. now you will see the panel but all the gauges are small and on de left side of the screen. go in to editor mode and drag the gauges to their position and make them bigger (enter a bigger nummer on size px) Now you need to test a little on how big you need them to be. When done save the panel and you should be good to go:thumbup: Ps you need the original file names to make it work. Good luck!:pilotfly:
-
Hi McMicha I was reading through the update details from the last update....1 of the fixes was on crashes with the P-51 panel.... I updated DCS to the last version. I did not made any changes as the ones described above... Now the P-47 panel works :D So there was sometghing wrong on ED side. Time to create some more panels:pilotfly: Greetings Naj-Treg
-
Hi Strike277 I used a little free tool called 'Mofiki's Coordinate Finder' Run the program and place your mouse cursor on the top left corner of the desired monitor you would like to use as your panel and press spacebar. Now the program gives you a X and Y coordinate. enter these X and Y coordinates (Pos. X / Pos. Y) in the ikarus software and it should place the panel on the correct screen. hopefully this helps you. Naj-Treg
-
Hello McMicha, Thankyou for the reply. I setup the files as you described, checked the module name in the export.log and renamed the files to the one the export log shows. Still get the crash when the P-47 get loaded. I created a mission with multiple planes and select the P-51, no problem panel and gauges working good. In the same mission i press esc ----> choose slot and select the P-47. Then my custom made panel loads. then DCS crashes. The only thing i changed is the panel background (for a P-47 panel) and re-sized and replaced the gauges. when not using the Ikarus software or remove my P-47 panel files the mod works fine. I am using the P-47 as a test bed....I have some more WWII mods and love to create some panels for them. here is the link to the P-47 mod: https://forums.eagle.ru/showthread.php?t=188526 kind regards, Naj-Treg
-
Hi. Thank you for this great tool! I really like it! I only have one question...Is it possible to add a panel for a mod plane? I use the P-47 mod wich is based on the P-51. I created its own panel with the files (copied the P51 files en renamed them for the P47) The moment i load a mission with the P47 it loads the panel but then DCS crashes.... probably i have a wrong code of lua somewhere or need add the P47 somewhere... I know how to setup a panel all the standard panels working good. But can someone tell me step bij step tell me how to add a not standard panel? Kind regards, Naj-Treg
-
Hi zionid, I created very basic mission just to test the working of the script. DCS version: 2.2.0.12843 Map: Normandy MIST version: 4.3.71 CTLD: latest update I edited the ChainHome.LUA the so the messages appear automaticly when they detect an enemy plane. To do: -download the attached mission (i put in with the mission the .lua files i used.not needed when you test the mission.) - start the mission -wait till message 'chain home radar is now **manned** - select F10 for picture' appears -go to radio menu--->F10.other--->F1. chain home radar..--->F3 turn picture report on/off--->F1. message on if correct you wil get the messages automaticly when radar detects an enemy. this should be around 5 or 6 minutes in the mission. When there are enemy planes detected you will get the message every 30 seconds with the updated bearing, range and altitude. If you want to ask manually for a radar picture you need to edit the ChainHome.LUA file. open the file with a editor and change the following line: ewrs.onDemand = false --Setting to true will disable the automated messages to everyone and will add an F10 menu to get picture / BRA message. To: ewrs.onDemand = true --Setting to true will disable the automated messages to everyone and will add an F10 menu to get picture / BRA message. when you edited the lua file you need to re-load it in the mission. to do this: go to the mission editor and load the mission. -go to the triggers menu - select trigger: ChainHome script -select DO SCRIPT FILE (ChainHome.lua) -select the edited Chainhome.lua file -save the mission I hope this will guide you in the right direction. Good luck, Naj-Treg ChainHome.lua CTLD.lua mist_4_3_71.lua ChainHome Test.miz
-
+1 :thumbup: Running Normandy only at the moment, so it would be nice to have an example mission to implement it correct in to my mission :) Naj-Treg
-
Thank you for the quick reaction :thumbup: I got the files now let the experiments begin:smartass: Greetings Naj-Treg
-
Hi and many thanks for all the effort you all put in all these mods! One little problem here.... i would love to download and try this mod but i cant download it :( Googledrive says: The desired file does not exist. Is there a way i can download it? Greetings Naj-Treg
-
Thank you very much! will try this:thumbup: Greetings Naj-Treg
-
Hi all, Currently am reading a book about the german nightfighters in the Netherlands during WWII. In here i read that the german pilots every xx seconds get the heading and altitude of an enemy plane. Is there a way in the mission editor to obtain enemy flight data and send it as a text or radio message and update it every xx seconds? I asked this question before but was looking for a MOOSE script. Did not got a solution on it so i would like to know if it's possible to achieve this in the mission editor. I would like to create a nightfighter mission using a random airtraffic script so you never know where the enemy is comming from. To achief this i need the same data (heading+altitude) as the pilots got back in 1940/1945 I know we don't have the right planes for it but i would love to try and find out if this could work. any help would be appreciated Greetings Naj-Treg
-
Hi to all mission building aces in here. I have a question about the MOOSE scripting tool. Is it possible to get the heading and altitude from an enemy plane as a text message wich gets updated every xx seconds? Currently am reading a book about the german nightfighters in the Netherlands. In here i read that the german pilots every xx seconds get the heading and altitude of an enemy plane. I would like to create a nightfighter mission using a random airtraffic script so you never know where the enemy is comming from. To achief this i need the same data as the pilots got back in 1940/1945 I know we don't have the right planes for it but i would love to try and find out if this could work. any help would be appreciated Greetings Naj-Treg
-
I wanted to do that, only problem is that the player can ask for a re-arm and re-fuel. When playing this way the recon plane has weapons. This is something I dont want to have for the recon plane at all times. All the other planes can carry weapons. Naj-Treg
-
Good day all, I have a question about setting up a recon plane. I am constructing a multiplayer mission wich can be flown from both sides. It's a WWII setup. To aquirre targets both sides needs to perfom a recon and land back @ base. For the allied side I use the TF-51 for the recon mission. Now I need a recon plane for the axis. For the recon I want an unarmed plane. Now for the question: Is it possible to assign a plane, for example the BF-109, and set it up unarmed and lock the possebility to re-arm the plane in the mission? Only this recon Bf-109 needs to be un-armed. I create other groups wich are combat ready. If this is possible how can i set it up? Naj-Treg
-
:thumbup: Thanks alot! it works:thumbup: This is exactly what i wanted to create. learned something new today:smartass: Spending more time mission building then flying lately. :doh: But i like it Naj-Treg
-
Thank you for your reply :thumbup: Scripting is a bit too much for me... Just starting with the basics of mission building and triggers. Will have a look on it later on. Naj-Treg