HILOK

hi everyone, happened twice to me + human wingman in two different missions (so basically 4 times) in nevada. yesterday and couple of days ago. here the highlights: - openbeta latest - hot start parking (no human startup) - extended ground time with running engines (20min+, then taxi) - during parking no messing with systems, just basic NAV / COM setup - no usage of ground power - 1st occurrence while parking (both jets), 2nd during taxi (both jets) - sequence: first my jet (server, so first to join), shortly after his jet (delay about the delta in join time) - "ELEC SYS" + "FLCS PMG/MAIN GEN" light, and some systems off (stby ADI, FCR, MIDS,...) hope that helps to reproduce. cheers hilok

@hollywood_315 thanks for adding the grey bars to your manual! great job :thumbup:

hey @Hollywood_315, thank you so much for your continued devotion to this project!! it has been a huge game changer for me, so that i am not even using DCS without it anymore! i see you keep updates coming regularly, and also update the manual accordingly, wich is a great thing. would it be possible that you somehow mark the changes within the manual text? e.g. vertical bars next to the changed paragraph are common practice in aviation. that would make it much easer to keep track with the frequent additions & changes (yes i am actually reading manuals :D) cheers HiLok

you're right! actually i should have taken the waterline into consideration as well. i was assuming the gun cross over the waterline in my calculations, which is only roughly the case. not sure what you mean, because the pitch ladder is the only reference you got to quantify the AOA, when using gun-cross & FPV over the HUD. ok, the point of my post was bringing this to your attention, so fair enough : )

hi deano, i appreciate your efforts. as much as you, i just want the viper flight model to be as accurate as possible : ) when comparing both HUD pictures on page 1, i believe that the pitch ladders should be graphically calibrated as well, cause they don't match (see magenta lines in pic below). and that means the AOAs can't be compared graphically. but the AOAs could be deduced in each pic separately. that's what i did (see green arrows). either method isn't super accurate anyway, but i think it serves for the purpose. so, although the corrected difference in AOA is not as great as before, it is still significant in my opinion: 13% thanks, HiLok

hi Theodore42, thanks a lot for taking the time to explain in all detail! actually my post was meant to second emmy's message, and i am confident it has nothing to do with AP or its usage. i should have been more clear probably. thanks anyway HiLok

i am experiencing this mainly after ramp start in self made missions, not so in the stock instant missions starting in air. maybe it has to do with the alignment process?

yes, but after switching to a preset on the DED as you describe, back on the c&i page (dobber left) you can use dobber up/down to place those little up/down arrows next to your UHF or VHF indication, and then the rocker switch allows switching presets.

listen, i'm just trying to help, no reason to react like this. AOA is not only a function of pitch, and you are saying you had an IAS of 150kt, which speaks for high AOA. admittedly, i can only speculate how deep aerodynamic effects (--> wakes, other jet exhaust) are implemented by ED, and how accurate the viper is physically modeled by now (--> exaggerated deep stall behavior)...that being said, deep stall, whether or not it is correct for the situation you got into, is a possibility. in this case afterburner has no effect, as far as i am informed. the only way out is using the MPO and getting the jet's pitch in sync with the oscillation.

you probably got yourself into deep stall. that's what your MPO (MANUAL PITCH OVERRIDE) switch is for ;)

hi DJ, you can use the ruler function within the ME as well as the ingame map to measure distance (and bearing). maybe handy to quantify your accelerate-stop-distance or landing distance. cheers

TM WT throttle extensions here's what i was able to measure using simple tools without disassembling the thing. so it may not be 100% precise, but should do anyway. angles (with respect to waterline): at full forward position 50° idle (not cutoff) 115° => travel angle (=difference) 65° thrust lever heights (gimbal to grip tops), approximate: left 15 cm right 17 cm from this data, i would estimate an extension by 6 cm, i.e. original length + 6 cm, would be a reasonable sweet spot between sufficiently increasing precision while keeping the throw within acceptable range. please tell me what you think, and if you see a chance that you could design something : ) i think there would be some demand within the community. at least, i hope so. thanks!

well to be honest, i haven't decided yet. but i think the solution must be figured out first, and would be independent of the extension length? anyway, i guess something between 2 and 6 cm should do the trick of improving precision, while keeping the grip's travel arc within an acceptable range.

TM WT throttle hi debolestis, just had a look at your cougar gimbal replacement. you really are ingenious! any chance you could make extensions for the thrustmaster warthog throttle grips? i.e. replace the shafts by longer ones? i guess this could be very interesting for a lot of people. thanks HiLok

yeah, that seems to be status quo. has anyone tried to implement triggered failures on a multiplayer/client aircraft using a LUA script? maybe this could be a workaround till the problem gets fixed. i sincerely hope ED will fix this soon, as it would open a whole world of new scenarios in mission design. cheers HiLok

just a quick follow up on my nevada script. works quite ok, occasionally some errors or plane crashes... : ) however, all jets taking off from RWY 25 at north las vegas crash at the end of the runway. maybe someone has an idea regarding this issue? here's the code, in case anybody wants to use (or correct) it: -- Author: HiLok 03/2019 -- Notes: local b757air=RAT:New("RAT_B757air") -- removed due to error: no valid destination found -------------------------------------------------------------------------------------------- -- Aircraft -------------------------------------------------------------------------------- local a320=RAT:New("RAT_A320") local b727=RAT:New("RAT_B727") local b737=RAT:New("RAT_B737") local b747=RAT:New("RAT_B747") local b757=RAT:New("RAT_B757") local cessna=RAT:New("RAT_Cessna") local huey=RAT:New("RAT_UH1H") -- AIR local a320air=RAT:New("RAT_A320air") local b727air=RAT:New("RAT_B727air") local b737air=RAT:New("RAT_B737air") local b747air=RAT:New("RAT_B747air") local cessnaair=RAT:New("RAT_Cessnaair") local hueyair=RAT:New("RAT_UH1Hair") -- std skins, std cruise level a320:DestinationZone() a320:ATC_Messages(false) -- Skins ----------------------------------------------------------------------------------- local a320skins={"American Airlines", "Frontier", "JetBlue"} local b727skins={"ZERO G", "UNITED Old", "Southwest", "FedEx", "American Airlines", "Delta Airlines", "Delta Airlines OLD", "Northwest", "UNITED"} local b737skins={"AM", "American_Airlines", "C40s", "Disney", "JA", "SouthWest Lone Star", "UPS"} local b747skins={"AF", "AI", "CP", "IM", "KLM", "LH", "NW", "TA", "QA", "TA"} local b757skins={"AA", "BA", "Delta", "DHL", "Swiss", "Thomson"} local cessnaskins={"Muster", "N9572H", "SEagle blue", "SEagle red", "USAF-Academy"} a320:Livery(a320skins) b727:Livery(b727skins) b737:Livery(b737skins) b747:Livery(b747skins) b757:Livery(b757skins) cessna:Livery(cessnaskins) -- AIR a320air:Livery(a320skins) b727air:Livery(b727skins) b737air:Livery(b737skins) b747air:Livery(b747skins) cessnaair:Livery(cessnaskins) -- Cruise FL ------------------------------------------------------------------------------- a320:SetFLmin(280) a320:SetFLmax(370) a320:SetFLcruise(350) a320air:SetFLmin(280) a320air:SetFLmax(370) a320air:SetFLcruise(350) b727:SetFLmin(280) b727:SetFLmax(360) b727:SetFLcruise(340) b727air:SetFLmin(280) b727air:SetFLmax(360) b727air:SetFLcruise(340) b737:SetFLmin(280) b737:SetFLmax(410) b737:SetFLcruise(370) b737air:SetFLmin(280) b737air:SetFLmax(410) b737air:SetFLcruise(370) b747:SetFLmin(280) b747:SetFLmax(390) b747:SetFLcruise(360) b747air:SetFLmin(280) b747air:SetFLmax(390) b747air:SetFLcruise(360) b757:SetFLmin(280) b757:SetFLmax(370) b757:SetFLcruise(360) cessna:SetFLmin(7) cessna:SetFLmax(115) cessna:SetFLcruise(85) cessnaair:SetFLmin(7) cessnaair:SetFLmax(115) cessnaair:SetFLcruise(85) -- Departures ------------------------------------------------------------------------------ -- all except Mina: "Beatty Airport","Boulder City Airport","Creech AFB","Echo Bay","groom Lake AFB","Henderson Executive Airport","Jean Airport","Laughlin Airport","Lincoln County","McCarran International Airport","Mesquite","Nellis AFB","North Las Vegas","Pahute Mesa Airstrip","Tonopah Airport","Tonopah test Range Airfield" a320:SetDeparture({"McCarran International Airport","North Las Vegas"}) b727:SetDeparture({"McCarran International Airport","North Las Vegas"}) b737:SetDeparture({"McCarran International Airport","North Las Vegas"}) b747:SetDeparture("McCarran International Airport") b757:SetDeparture("McCarran International Airport") cessna:SetDeparture({"Beatty Airport","Boulder City Airport","Henderson Executive Airport","North Las Vegas"}) huey:SetDeparture({"Boulder City Airport","Henderson Executive Airport","McCarran International Airport","Nellis AFB","North Las Vegas"}) -- Destinations ---------------------------------------------------------------------------- a320:SetDestination({"RAT_zone_NE","RAT_zone_SE"}) b727:SetDestination({"RAT_zone_NE","RAT_zone_SE"}) b737:SetDestination({"RAT_zone_NE","RAT_zone_SE"}) b747:SetDestination({"RAT_zone_NE","RAT_zone_SE"}) b757:SetDestination({"RAT_zone_NE","RAT_zone_SE"}) cessna:SetDestination({"Beatty Airport","Boulder City Airport","Henderson Executive Airport","North Las Vegas"}) huey:SetDeparture({"Boulder City Airport","Henderson Executive Airport","McCarran International Airport","Nellis AFB","North Las Vegas"}) -- AIR a320air:SetDestination({"McCarran International Airport","North Las Vegas"}) b727air:SetDestination({"McCarran International Airport","North Las Vegas"}) b737air:SetDestination({"McCarran International Airport","North Las Vegas"}) b747air:SetDestination("McCarran International Airport") cessnaair:SetDestination({"Beatty Airport","Boulder City Airport","Henderson Executive Airport","North Las Vegas"}) hueyair:SetDeparture({"Boulder City Airport","Henderson Executive Airport","McCarran International Airport","Nellis AFB","North Las Vegas"}) -- Traffic Density ------------------------------------------------------------------------- a320:Spawn(2) b727:Spawn(2) b737:Spawn(2) b747:Spawn(3) b757:Spawn(3) cessna:Spawn(3) huey:Spawn(1) -- AIR a320air:SetTakeoff("air") a320air:Spawn(2) b727air:SetTakeoff("air") b727air:Spawn(2) b737air:SetTakeoff("air") b737air:Spawn(2) b747air:SetTakeoff("air") b747air:Spawn(2) cessnaair:SetTakeoff("air") cessnaair:Spawn(3) hueyair:SetTakeoff("air") hueyair:Spawn(1) -- EOF -------------------------------------------------------------------------------------

hmmm, interesting. and strange. because you are describing what i would have expected, when looking at the example code and the doc. but in fact i got the errors (see posts above), when implementing zones without the command DestinationZone...

:D sure, that's coding, right? if you have time, could you pls take a moment and clarify how the DestinationZone() property/command(?) affects all aircraft spawned, although i applied it to the a320 group only? thanks

thanks, funkyfranky. meanwhile i got the traffic back during mission runtime -no idea what caused THAT problem. anyway...after some trial & error, i finally got it working, but frankly i dont understand exactly how :D new code (remainder of the code posted before: same same) -- Fixed Destinations a320:SetDestination({"RAT_zone_NE","RAT_zone_SE"}) a320:DestinationZone() --a320:ReturnZone() --a320:SetDestination({"McCarran International Airport","North Las Vegas"}) --a380:SetDestination() b727:SetDestination({"RAT_zone_NE","RAT_zone_SE"}) --b727:ReturnZone() --b727:SetDestination({"McCarran International Airport","North Las Vegas"}) b737:SetDestination({"RAT_zone_NE","RAT_zone_SE"}) --b737:ReturnZone() --b737:SetDestination({"McCarran International Airport","North Las Vegas"}) b747:SetDestination({"RAT_zone_NE","RAT_zone_SE"}) --b747:ReturnZone() --b747:SetDestination("McCarran International Airport") b757:SetDestination({"RAT_zone_NE","RAT_zone_SE"}) --b757:ReturnZone() --b757:SetDestination("McCarran International Airport") cessna:SetDestination({"Beatty Airport","Boulder City Airport","Henderson Executive Airport","North Las Vegas"}) -------------------------------------------------------------------------------------------- apparently this line did the trick: a320:DestinationZone() but i dont get why it would affect all other a/c types as well. maybe you could give me a little hint? anyhow, i am very glad it is now working, and it does like a charm :thumbup: thanks

thanks for your assistance, funkyfranky! i thought i solve the problem by letting the mentioned a/c go to zones instead, but now i am not getting any traffic at all! not even air spawned traffic that worked well before. no error messages either. any ideas? new code (did not touch the rest of the code): -- Fixed Destinations a320:SetDestination({"RAT zone NE","RAT zone SE"}) --a320:SetDestination({"McCarran International Airport","North Las Vegas"}) --a380:SetDestination() b727:SetDestination({"RAT zone NE","RAT zone SE"}) --b727:SetDestination({"McCarran International Airport","North Las Vegas"}) b737:SetDestination({"RAT zone NE","RAT zone SE"}) --b737:SetDestination({"McCarran International Airport","North Las Vegas"}) b747:SetDestination({"RAT zone NE","RAT zone SE"}) --b747:SetDestination("McCarran International Airport") b757:SetDestination({"RAT zone NE","RAT zone SE"}) --b757:SetDestination("McCarran International Airport") cessna:SetDestination({"Beatty Airport","Boulder City Airport","Henderson Executive Airport","North Las Vegas"}) trigger zones as shown in image attached. thanks HiLok

thanks for your reply, rudel. but, assuming you are right, would the traffic still take-off and land on the designated airports? because this is what the RAT airplanes do. and they also appear on the allied flight list in the briefing... or is this independent of the RAT settings? from the figures in the error msg, it appears only aircraft that get spawned on ground are affected, except for the cessnas. this is also reflected during runtime: at mission begin, there are no a/c on mccarran nor on vegas north.

hi guys, this is really a fabulous addition to DCS! thank you very much!! i am new to this, and the link for the doc in one of the introductory posts is dead. so, i took one of the instant mission scripts, and adapted it to my needs, but i am getting errors at mission start. could someone please have a look and tell me what's wrong? error msg i get attached... thanks everyone HiLok

thanks for clarification! I also noticed that the fuel check buttons won't work with fuel qty set to off.

hi everyone, is this mod working on the current 2.5.xx openbeta? thanks

thanks zius for your recommendations. much appreciated! actually, i don't think these grips are too rare, because they were and most probably still are used in a lot of aircraft incl. rotorcraft. i intend to mod it with debolestis' sets in order to use it on a warthog base : )