D3adCy11nd3r
-
Posts
61 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by D3adCy11nd3r
-
"Generating First Mission. 10:02h passed. Next mission scheduled at: 11:02, 6.4.2001. METAR 061102 14008KT CAVOK NSW SCT168 Q1007= Please Wait... possible failure ELEVONSERVINNERRIGHT 1H19 Durée 52 probability: 90 possible failure RWRANTREAR 0H51 Durée 16 probability: 47 possible failure DOPPLER_UNIT 0H7 Durée 4 probability: 46 possible failure GTS 1H21 Durée 28 probability: 77 possible failure Failure_PP_EngL_Nozzle_CS 0H13 Durée 21 probability: 29 possible failure AOASENSOR 0H28 Durée 33 probability: 2 possible failure ELEVONSERVOUTERRIGHT 1H44 Durée 35 probability: 73 possible failure BACKUPGENERATOR 0H8 Durée 45 probability: 29 ..\..\..\..\..\..\..\bin\luae.exe: Scripts/ATO_Generator.lua:45: attempt to index field '?' (a nil value)" So it gets further than the file I had
-
Okay changed the code now I am getting "..\..\..\..\..\..\..\bin\luae.exe: Scripts/ATO_Generator.lua:1: unexpected symbol near '∩'" Followed by the traceback When i run the skip mission it does not generate just closes. So inputs would be [y] and then [enter] and it shuts the window down. No errors thrown on skip mission.
-
Sorry, I flew a mission yesterday then got busy. The script does work, the failures do happen [YAY] However this morning when I tried to generate a mission I get "Generating First Mission. 07:40h passed. Next mission scheduled at: 08:40, 6.4.2001. METAR 060840 00006KT CAVOK NSW SKC Q1035= Please Wait... possible failure FR24RADIO 1H10 Durée 48 probability: 54 possible failure HYD_PUMP_2_FAIL_100 1H35 Durée 31 probability: 82 possible failure MAINGENERATOR 1H56 Durée 41 probability: 25 possible failure BCKGYRO 0H48 Durée 4 probability: 80 possible failure ELEVONSERVINNERLEFT 0H5 Durée 29 probability: 9 ..\..\..\..\..\..\..\bin\luae.exe: Scripts/ATO_Generator.lua:44: attempt to index field '?' (a nil value) stack traceback: Scripts/ATO_Generator.lua:44: in main chunk [C]: in function 'dofile' Scripts/MAIN_NextMission.lua:156: in main chunk [C]: in function 'dofile' Scripts/BAT_FirstMission.lua:195: in main chunk [C]: ? I:\SteamLibrary\steamapps\common\DCSWorld\Mods\aircraft\FA-18C\Missions\EN\Campaigns\Hornet over PG>" Have not changed anything. When I remove the script chunk it works.
-
Got flying one now
-
@Miguel21 and @Pb0_CEF I am running the f/a18c right now [since it is the only craft I know well enough to handle failures] I added the lines of codes to ATO_Generator.lua When generating the first mission it did show it added the failures to the mission. [possible failure ELEVONINNERLEFT 1H40 Durée 54 probability: 9 possible failure Failure_PP_LeftAMAD_OilLeak 1H16 Durée 57 probability: 14 possible failure Failure_Fuel_ExtTankTransferL 0H33 Durée 36 probability: 24 possible failure HYDR2PUMP 0H57 Durée 14 probability: 2 possible failure REVERSER 1H2 Durée 49 probability: 9 ] They do appear to be randomized [not the same for each generation.] However they do not activate the random failures in the mission planer (not sure if they are supoused to and I am sure I am doing something wrong as far as the "This will work if and only if the failures associated with your aircraft are already present in base_mission.miz If it is not the case, it will have to be modified by hand ...." Part is concerned.
-
Thank you sir. That makes sense.
-
I am still having an issue getting the Radio tune to work correctly. I reinstalled vaicom and got it to work once outside of the game, I am having to hop into rio seat to set the radio channel then back into the drivers seat, its effective but damn it sucks LOL
-
@Miguel21 My Base_mission.MIZ file is encrypted (-.-) So I can not edit any of the code inside it. I am really just looking to add in the random script. Thanks man
-
Can I wait, yes, will I probably not LOL. The random one is more what I am looking for since I don't really want to run into the exact same failure every time. Question the script, what are the base chances or is everything "random"? Thank you
-
Then we need a rallying cry. I would love to set a 10 percent blanket failure on all systems from the ramp. IRL the plane is not perfect and in a war zone less so.
-
Tacan Tune [xray-yankee] [first number, usually zero] [second number 1-9, usually] [third number 0-9, usally] I always forgot about the first number and could rarely get it to catch without it. IE tacan tune x-ray 038 = 38x
-
Remember that the UHF has 5 "encoders" to tune the radio, the VHFs have 4. I typically focus on the harder to reach stuff [aka the back of the pit] so that flipping stuff while maneuvering becomes a bit easier. Be careful though. I built one box a few months ago for stupid cheap. [60 bucks or so] then built 3 more.. You can never have to many buttons.
-
Any update on the radio tune command not working and missing in the aliases?
-
Is there any way to add random failures in without having to go in and hit the random button on the mission editor?
-
You wouldn't that burden would be placed on the "pilot" to bind it to the correct switch, but give the option. Most planes have a flaps "axis" or single states with degree adjustments. I am aware that a blanket toggle state would not apply to every single switch in the game. But why do some "spring load". Meaning if I turn off the input they return to "default" position and others latch. Make all of them latch, or all of them spring load but make them consistent so that as a pit designer, or regular player you have the option without having to spend an hour editing the .lua for inputs. That is all i am saying.
-
The options menu has to have the ptt button held the entire time you are talking to it. You can jump staight to the f10 menu by saying "take 10" then command from there.
-
Alright, I know i am probably one of the very very few, and realism is the ultimate goal here. Can we PLEASE standardize the toggle switch inputs. IE if a switch is only latched when the input is down and returns unlatched when the input is up do it for ALL toggle switches. If it is a toggle by press IE if the button is pushed the toggle is latched until the button is pressed again do that for ALL the toggle switches. We should not have to spend more time in .lua files modifying inputs than we do flying the jets. Like I said most people do not have the inputs to bind every switch I get that, but for those who do please just standardize them. Rant over really love the jets, keep up all the hard work. Thank you.
-
Bpmorris, I was screaming at it last night trying to get it to recognize radio tune before I noticed the command was missing, lol. It seems like it is just flat missing, I wonder if downloading an older version f the rioai extension would work, then just updating it...
-
It is set to 124.600 the game states it needs to be set to 127.600. I looked in the mission editor last night and got the freq to change to the correct one but noticed I had to stennis carriers and no vinson... Going to redownload and see if that will fix it.
-
@Freightdog, try the options take route, even in VR I can usually run my f10 units without needing to export them.
-
Okay, i have done a lot of searching and have come up with nothing. My command list does not include radio tune (like it does with tacan tune) i have no idea how to add it back, i have tried the finish and copy to the profile, va states i have no missing aliases and require no further action but radio tune does not work at all.
-
Yeah some of those are crazy failures..
-
Encase someone runs across this forum looking for an answer to the GPS position being wonky, change the date to 2001+ And for whatever reason I can not talk to the ship on the tomcat over PG. The ship frequency do not seem to work.
-
" 14 Jan. 1992: mid-air collision with a T-34C over Corpus Christi, TX. The Tomcat had an unsafe landing gear and the T-34 was checking it and later wrapped itself around the Tomcat's right wing. Both aviators in the T-34 were killed. The wreckage was left on the Tomcat's wing. The Tomcat land at the NAS there but had extensive damage." I think that may be a fair assessment of the tanky nature of the a/c
-
Fuel Dump Toggle Switch Behavior (stable build)
D3adCy11nd3r replied to Bones1775's topic in Controller Questions and Bugs
I had the problem pop back up today, even after I had them working previously. My changes in the .lua are still accounted for but even the modified lines are now acting like the unmodified lines, so I am convinced there is a moving variable somewhere.. IDK where but it has to be in there. I am going to admit defeat because it almost drove me crazy to get a fix last time. Any one finds something out let me know and I will try it.