Snapper

Thx for the new version. Now it works in PG, with RAT and with a carrier inside it's battlegroup. :thumbup: Now we need a final carrier with fixed spawn points and working elevators from ED. Looking forward for the tanker addition.

Hi Maverick, is your Carrier alone or within a group? And further does he stay for more than 60 minutes in formation with your Carrier? Is it Persian Gulf too? Don‘t get me wrong. The script itself and all the Moose and RAT is great. I am still at the beginning with DCS and it’s capabilities.

Ah sorry I missed that Navy Crew Mod. I deleted them inside my mission and you should be able to open the file now. I can't do further testing until tomorrow. Will try than with just a carrier instead of a group. Carrier_Test.miz

Same here. I deleted the local as you suggested and it seems to work in the beginning. After 58 minutes of stable formation with the Stennis the helicopter did a 180 degree turn and started a pattern away from the carrier. The last times I saw that the Helo will land onboard the Stennis but this time it choosed the closest frigate on its course back to land. Would be ok that far but the helo will stay parked onboard the frigate for around 34 minutes and than disappears. There comes no respawn. I attached my missionfile and both skripts so you can see it yourself. Thx for your help :thumbup: Carrier_Test.miz Carrier_Formation.lua RAT.lua

Thx for your alternative Highwayman-Ed. Will try that out. Have to check my logfile too. Maybe I can find the cause there. Right now I think when using VR random traffic is not such a big deal. Still trying to get used to the low visibility at distance. Maybe I used Smartscaling way to long :(

No, I only placed some static Hornets, Tomcats and Navy personal on the deck. There is no RAT generated airtraffic on the carrier yet. Here is my current RAT script --Creating RAT objects local c130=RAT:New("RAT-C130") c130:SetDeparture("Al Dhafra AB", "Al Maktoum Intl", "Al Minhad AB", "Sharjah Intl", "Fujairah Intl") c130:ATC_Messages(false) c130:StatusReports(false) c130:Spawn(2) local f15c=RAT:New("RAT-F15") f15c:SetDeparture("Al Dhafra AB", "Al Maktoum Intl", "Al Minhad AB", "Sharjah Intl", "Khasab", "Fujairah Intl") f15c:ATC_Messages(false) f15c:StatusReports(false) f15c:SetSpawnInterval(180) f15c:Spawn(3) local c17=RAT:New("RAT-C17") c17:SetDeparture("Dubai Intl") c17:StatusReports(false) c17:ATC_Messages(false) c17:Spawn(1) --Activate uncontrolled planes at Al Minhad AB local hornet=RAT:New("RAT_Hornet", "Hornet Al Minhad AB") hornet:SetDeparture("Al Minhad AB") hornet:SetDestination("Al Dhafra AB", "Al Maktoum Intl", "Al Minhad AB", "Sharjah Intl", "Khasab", "Fujairah Intl") hornet:ATC_Messages(false) hornet:StatusReports(false) hornet:SetSpawnDelay(6) hornet:SetSpawnInterval(0.5) hornet:Uncontrolled() hornet:ActivateUncontrolled(30, 120, 120, 0.5) hornet:ContinueJourney() hornet:Spawn(10) local warthog=RAT:New("RAT_A10", "A10 Al Minhad AB") warthog:SetDeparture("Al Minhad AB") warthog:SetDestination("Al Dhafra AB", "Al Maktoum Intl", "Al Minhad AB", "Sharjah Intl", "Khasab", "Fujairah Intl") warthog:ATC_Messages(false) warthog:StatusReports(false) warthog:SetSpawnDelay(2) warthog:SetSpawnInterval(0.5) warthog:Uncontrolled() warthog:ActivateUncontrolled(360, 420, 420, 0.5) warthog:ContinueJourney() warthog:Spawn(5) --Dubai Intl Outbound traffic local b737skins={"Air Berlin", "American_Airlines"} local b737=RAT:New("RAT_B737", "B737 Outbound") b737:SetDeparture("Dubai Intl") b737:SetDestination("RAT Zone") b737:Livery(b737skins) b737:SetMaxRespawnTriedWhenSpawnedOnRunway(0) b737:StatusReports(false) b737:SetSpawnDelay(320) b737:SetSpawnInterval(20) b737:SetTakeoff("hot") b737:RespawnInAirNotAllowed() b737:RespawnAfterTakeoff() b737:Spawn(2) local a380skins={"Air France", "Emirates"} local a380=RAT:New("RAT_A380", "A380 Outbound") a380:SetDeparture("Dubai Intl") a380:SetDestination("RAT Zone") a380:Livery(a380skins) a380:SetMaxRespawnTriedWhenSpawnedOnRunway(0) a380:StatusReports(false) a380:SetSpawnDelay(120) a380:SetSpawnInterval(10) a380:SetTakeoff("cold") a380:RespawnInAirNotAllowed() a380:RespawnAfterTakeoff() a380:Spawn(2) local b757skins={"Delta", "DHL"} local b757=RAT:New("RAT_B757", "B757 Outbound") b757:SetDeparture("Dubai Intl") b757:SetDestination("RAT Zone") b757:Livery(b757skins) b757:SetMaxRespawnTriedWhenSpawnedOnRunway(0) b757:StatusReports(false) b757:SetSpawnDelay(180) b757:SetSpawnInterval(10) b757:SetTakeoff("cold") b757:RespawnInAirNotAllowed() b757:RespawnAfterTakeoff() b757:Spawn(2) --High Level Transit west-east local yak_westeast=RAT:New("YAK West-East") yak_westeast:SetSpawnDelay(30) yak_westeast:SetSpawnInterval(120) yak_westeast:SetTakeoff("air") yak_westeast:DestinationZone() yak_westeast:SetDeparture({"Zone West", "Zone East"}) yak_westeast:SetDestination({"Zone West", "Zone East"}) yak_westeast:SetFLmin(300) yak_westeast:SetFLcruise(310) yak_westeast:SetFLmax(320) yak_westeast:Spawn(3) Tried to use only parts of the above but without luck. There has to be something really wrong.

I have the same problems on PG you reported already. My SAR Helo will takeoff, fly away from the ship and than lands again. After that it's parked on the carrier and there is no respawn. I am using RAT too and tried your fix with reducing the liveries, but without luck. Is it ok to run different scripts and mission start like a RAT file and the Rescue Helo Skript or should it be one file?

As Wags stated nothing has changed, so Ed's plan still is to give us the announced features during October.

Thx for your reply. Will try to restrict the airfields with SetDestination options than and see what I get. Cheers

Hi, I just created my first F18 training mission with elements from Moose and RAT to get some random elements. I used some civil outbound traffic from Dubai, some planes traveling between two zones and the new script for the later activation. Maybe you can help me to get further by answering my questions. 1. I thought I should be able to see contrails from the heavies during the mission. Is there a Altitude in DCS which gives you contrails for planes like 757. I can see those when switching the camera to them but not from ground or from my plane. 2. The script for the later activation will let these planes takeoff,fly to a random airfield, Land there and gets deactivated afterwards. After that it may become active again and the process restarts. I ran in trouble because jets crashed by trying to land at a short runway. After that the jet respawned on that airfield and wasn’t able to start without crashing which ends in a loop. Any ideas to restrict airfields from the random script? I used the following script with F18s and A10s -- Skins local cessnaskins={"Blank", "D-EKVW", "HellenicAF", "Muster", "N9672H", "SEagle_blue", "SEagle_red", "USAF-Academy", "V5-BUG", "VH-JGA"} local cessna=RAT:New("RAT_CESSNA", "Cessna Henderson") cessna:SetDeparture("Henderson Executive Airport") cessna:Livery(cessnaskins) cessna:SetSpawnDelay(30) cessna:SetSpawnInterval(0.5) cessna:Uncontrolled() cessna:ActivateUncontrolled(30, 120, 120, 0.5) cessna:ContinueJourney() cessna:Spawn(44) Greetings from Germany

You're right I thought there was a newer one but the statement was from a older post. Have to try it myself tomorrow to get data. Will post it tomorrow I think, than we can compare.

DCS released a new Patch today and other people reported there was a Nvidia driver update too. Did you check your Nvidia settings too? Might help to know which component causes this. CPU,GPU,RAM...

I am for shure no DCS Expert right now but my system is nearly the same accept the amount of RAM. Maybe you are running out off RAM. I readed a lot about RAM issues during the last weeks. Not shure they fixed that now. What happens when you use your screen instead for testing? Did you try to find out what component causes this? I thought it is my CPU but just noticed that my 1080 TI is running at 100% sometimes while my plane is still on the ground. I am still at the beginning of my DCS journey and hopefully it will be longer that time. Maybe give Process Lasso and MSI Afterburner a try to take a look what is causing your issues. Another cause could be RAM and Pagefile. Are you running a SSD? I there enough freespace? Just my thoughts maybe it helps :)

Forcing IPD and changing the value to 55 together with Gamma 2 and PD on 1.4 did the trick. It’s much better now. I did a reset of my shaders too. And I found out that my Updater was outdated. Now I am really running the latest Beta Version. Zoom alone changed nothing.

When your headphone is connected you should be able to select the output you wish by choosing it via windows taskbar (Speaker).

I think it’s just a to high brightness and was searching for a setting to reduce it. Will try the zoom anyway but can’t believe that this really is the solution for it.

Should be the last Beta build I think. The screen with the settings is from the Howto about VR and I used the same right now. Did they change HDR and DS in the stable version? Leaning forward helps but I am still irritated by the brightness/shimmering of these indicators.

Hi, I am a new Occolus Rift user and now I really understand the 3D WOW-Effekt after my first flight. Before that I was used to run 3 Screens and TrackIR. Still trying to find the best settings inside DCS. Already watched some videos and readed a couple of threads here. The new only think that annoyed me is that I can’t read my Caution lights. It’s pretty hard to read even the Master Caution, when you don’t know it you could assume it as two yellow bars. All lights have a to strong brightness/blooming even my mouse cursor is glowing. Especially during night missions. I tried to reduce the brightness but it didn’t help. The Caution lights at the front panel are unreadable. It seems the brightness is just to strong and dimming did not take Effekt. Tried PD between 1-2 without Effekt. HDR is not aktiv. Used the setting from a VR video for DCS. Any ideas to solve that or is it simply a Work in Progress or Rift Resolution problem which can not be solved? Running a 4790K @ 4 Ghz, 1080Ti, 32 GB RAM, Occolus Rift RV1

Yeah tried Gamma between 1 and 1.5 1 caused dark spots on the consoles at Night. 1.5 is what I use now I think. I think it’s similar to blooming and seems way to strong at the moment. Same goes for the mouse cursor when it switches to green over a clickable switch.

Isn‘t this one OFF or ON only? I am using the settings from the „All VR guide“ https://forums.eagle.ru/showthread.php?t=194778

Hi, I am a new Occolus Rift user and now I really understand the 3D WOW-Effekt after my first flight. Before that I was used to run 3 Screens and TrackIR. Still trying to find the best settings inside DCS. Already watched some videos and readed a couple of threads here. The new only think that annoyed me is that I can’t read my Caution lights. It’s pretty hard to read even the Master Caution, when you don’t know it you could assume it as two yellow bars. I tried to reduce the brightness but it didn’t help. The Caution lights at the front panel are unreadable. It seems the brightness is just to strong and dimming did not take Effekt. Tried PD between 1-2 without Effekt Any ideas to solve that or is it simply a Work in Progress or Rift Resolution problem which can not be solved? Running a 4790K @ 4 Ghz, 1080Ti, 32 GB RAM, Occolus Rift RV1

Kurzes Update nach einem weiteren Flug gestern Abend. Geflogen wurde die selbe Mission und wir befanden uns als Pig 1.1 und Pig 1.2 in der selben Gruppe/Flight. Dieses Mal klappte die Verständigung mit ATC teilweise. Ich konnte als Pig 1.1 alle Funksprüche hören also sowohl meine als auch die von Pig1.2 und die Antworten von ATC. Pig1.2 selbst konnte nicht immer eine akustische Antwort hören aber die Antworten immer in Textform lesen. Warum man als 2Ship nicht gemeinsam auf die Runway kann ist mir schleierhaft. Ich bekam die Genehmigung und 1.2 sollte warten. Beim Tanker gab es dagegen keine Probleme mehr mit den Comms. Es scheint also generell möglich zu sein 2 Clients innerhalb einer Gruppe zu haben. Muss das nächste Mal testen ob es zuverlässiger funktioniert wenn man nicht in der selben Gruppe fliegt. Insgesamt scheint es als ob DCS in seiner Logik noch nicht darauf ausgelegt ist. Ich kenne es aus einer anderen SIM jedenfalls so das ein 2Ship oder 4Ship als Einheit verstanden werden. Sprich Lead und ggf. Element Lead sprechen mit ATC etc. und alle Maschinen erhalten entsprechende Vektoren etc. oder werden auch in Reihe zum Tanken aufgefordert. Aber vielleicht kommt das ja noch :thumbup:

Werde es mal probieren sobald mein Kumpel wieder verfügbar ist. Komme dann mit Rückmeldung.

@MasterZelgadis Ja, das wäre der nächste Schritt gewesen. Natürlich wäre es mir lieber wenn es innerhalb einer Gruppe funktionieren würde. Test steht noch aus. @Nirvi - die Radios stehen auf den Frequenzen für Nellis (UHF 327.000, VHF AM 132.550, VHF FM 38.700) - EasyComms ist bei uns beiden deaktiviert - Benutzen beide einen Hotas Warthog und funken über den Radio Switch (forward), worauf das VHF AM Menü Ingame geöffnet wird - der Tanker hat seine Frequenz und wurde über VHF AM nach Wechsel auf seine Frequenz kontaktiert und reagierte auch auf Anfrage von Nummer eins, ich konnte auch auftanken. Tacan funktioniert auch. Okay, funktionierte für Nummer2 nicht, da keine Antwort vom Tanker kam. Fliegt ihr den generell immer noch in separaten Gruppen mit z.B. 2 Leuten?

Nein, sorry er fliegt in DCS auch eine A10C wie ich selbst. ich wollte damit andeuten das wir sonst eine andere Simulation fliegen und dort eben die Viper ;)