Cornelius

Just tried it on Caucasus map. Now with liveries: local a380=RAT:New("RAT-A380") a380:SetCoalitionAircraft("neutral") a380:SetCoalition("sameonly") a380:SetTakeoff("cold") a380:Spawn(5) local b727=RAT:New("RAT-B727") b727:SetCoalitionAircraft("neutral") b727:SetCoalition("sameonly") b727:SetTakeoff("cold") b727:Spawn(10) local b737=RAT:New("RAT-B737") b737:SetCoalitionAircraft("neutral") b737:SetCoalition("sameonly") b737:SetTakeoff("cold") b737:Spawn(10) local a380skins={"Air France", "BA", "China Southern", "Clean", "Emirates", "KA", "LH", "LHF", "Qantas Airways", "QTR", "SA", "TA"} local b727skins={"AEROFLOT", "Air France", "Alaska", "Alitalia", "American Airlines", "Clean", "Delta Airlines", "Delta Airlines OLD", "Hapag Lloyd", "Lufthansa", "Lufthansa Oberhausen Old", "Northwest", "Pan Am", "Singapore Airlines", "Southwest", "UNITED", "UNITED Old", "ZERO G"} local b737skins={"Air Algerie", "Air Berlin", "Air France", "airBaltic", "Airzena", "AM", "American_Airlines", "British Airways", "C40s", "Clean", "Disney", "EA", "easyjet", "FINNAIR", "HARIBO", "JA", "Jet2", "kulula", "LH", "Lufthansal cessnaskins={"Blank", "D-EKVW", "HellenicAF", "Muster", "N9672H", "SEagle_blue", "SEagle_red", "USAF-Academy", "V5-BUG", "VH-JGA"} a380:Livery(a380skins) b727:Livery(b727skins) b737:Livery(b737skins) This is working as expected. But when I add: local b757=RAT:New("RAT-B757") b757:SetCoalitionAircraft("neutral") b757:SetCoalition("sameonly") b757:SetTakeoff("cold") b757:Spawn(10) local b757skins={"AA", "BA", "C-32", "Delta", "DHL", "easyJet", "Swiss", "Thomson"} b757:Livery(b757skins) and one new template plane, not one plane is spawning. And even when I revert everything: No plane is spawning. Tried this also with adding a Cessna instead of an b757 - the same... Maybe it has something to do with openbeta?

Hello, I really need some help, this Moose-RAT-Thing is driving me crazy. :badmood: I'm able to successfully create some group of airplanes: local a380=RAT:New("RAT-A380") a380:SetCoalitionAircraft("neutral") a380:SetCoalition("sameonly") a380:SetTakeoff("cold") a380:Spawn(5) local b727=RAT:New("RAT-B727") b727:SetCoalitionAircraft("neutral") b727:SetCoalition("sameonly") b727:SetTakeoff("cold") b727:Spawn(10) local b737=RAT:New("RAT-B737") b737:SetCoalitionAircraft("neutral") b737:SetCoalition("sameonly") b737:SetTakeoff("cold") b737:Spawn(10) Then suddenly, when I try to add one more group, all planes disapear (no spawn) in the mission. Even when I revert the changes in the lua file and delete the new group - all planes are gone. This happens randomly sometimes also when I even add the second group of planes. At some point I were able to get it back working, when I delete and recreate the trigger, which executes the moose.lua & Rat.lua. Sometimes I have to delete everything. I spend some hours on this problem, but there's no pattern recognizable. I'm on Open Beta 2.5.3.22877 and the Persian Gulf Map. :helpsmilie::helpsmilie:

In this forum there are probably 95% armchair pilot opinions. Then probably everyone should shut up and the forum could be closed. Great contribution :thumbup: And instead of atributing to him, he'd demand a 100% realistic FM, one should exchange experiences about the VNSL landings and then come to a judgement whether the criticism is justified (the developers are of course also welcome, but well, you know) Wasn't that EA where the users can contribute to the development?

No, it hasn't. Maybe a little. But it's very important for him, and he doesn't get any answers for some time. Please cut him some slack, altough you are waiting longer... Anyway, I find these switch behaviours also very annoying.

sounds like it has something to do with this: https://forums.eagle.ru/announcement.php?f=555 ?

Is it possible, that someone from the devs could explain, what happend to the raindrops? Maybe they were just borrowed from ED and had to be returned? No one knows...

your wife :D

"A limited functionality Iceman AI piloting the aircraft in single-player when switching to the rear cockpit" https://www.digitalcombatsimulator.com/en/shop/modules/tomcat/

This is really an issue. I have to use nightvision, to get to the runway.

That's what this thread is all about. Despite an incorrect alignment position, the position of the own aircraft on the moving map is correct. 1. Post 5. Post Conclusion: 1 Week has gone by and the whole issue inflated to 4 pages.

Thank you for your answer Ramsay, but I don't get it. Why should it show an alignment error? Should it not act like correctly aligned, with that data you fed it, including wrong coordinates and wrong position on map?

:D

If the INS is ONLY coupled with GPS in IFA Mode, how come that the moving map knows your correct position, despite you aligned with wrong coordinates and the mode selector knob went to" NAV" after "INS GND"? (You don't even have to touch the mode selector after alignment) I think it's a minor bug. As I am no expert I would suspect the moving map-feature relies on the Navigation system and is not linked seperately e.g. with the pilots mobile phone...

Sehenswerte halbe Stunde. Tornado in DCS... :thumbup:

What is SVA ?

Oh, Sorry! Wrong Emoji. It should wave it's hands for attention, not cheer. Maybe something like this :helpsmilie: would have been better.

:cheer3nc:

it goes round in circles... :wacko:

we tried it already.. And regarding your second point: SINS and IFA are the only alignment modes in which neither aircraft present position nor local magnetic variation are required to be entered by the pilot before starting the alignment process. Pocket Guide, p57

And at the end we're again at this point:

As the work for newer projects has to progress, there's sadly no Razbam-member available here in the AV8B forum spending chill pills. One video per month does not seem to be enough... But at the end I'm sure a new "harrier-update-wave" will occur in the near future, when the other plane is put on hold. something like that :rolleyes:

+1

Just tried it myself. It alligns perfectly with completely wrong coordinates, without switching to IFA or something else. This seems to make the whole alignment process useless. :huh: EDIT: O.K. tried it again. It's only the moving map. Wrong coordinates stay wrong.

Shouldn't the INS be linked with the GPS only in IFA mode?