Doum76

Small tip :) Next time, if you can't look at your Fuel state when getting in the groove, when you trap, as you get slinged back by the wire, as you take a sip if your cold ones, look at your fuel state :P if it's close to 900 lbs, it's merely not enough for a pattern, yell at teh ground crew to give some cold ones to your bird as well. :P Orrrrrr Don't drink and fly :P

Why we would get this if it ain't working as this in RL? Just do as RL pilot does, as Lex said and as stated in the NATOPS «A1-F18AC-NFM-000.pdf» Make sure you'Re at 33.000 LBS or leff of Fuel, just sim it. :) If you limit the hook down with those things, people simming the real Hornet Startup procedures will have fun doing their 4-down-check before taking off, since you can take off with 51.900 lbs on carrier and field, which is over the GW of 33,000 lbs needed to trap....

Small question, i see everyone says after hook up, retract launch bar, but it simply retract itself on weight off wheels asap you're airborn when you launch, no retract the switch needed, how's is it suppoed to work in RL? Cuz so far i enver retract my switch, i lower it, attach to the shuttle (Pressing U) then i launch, as i leave the deck it simply retract itself by the time i raise gear and flaps..

Hi, Once in a while i press the Hook Ti Catapult button/key (Default U key) while being a bit too much angled, off from cat launch line, resulting in a bad miss alined hook up to the shuttle, but the bird never launch no matter how much AB i give, it just stays there, resulting i need to hop in a new bird and restart. The option would be quite simple, make the Hook bind, an option like lots of toggle keys, once Hooks, repressing it unhooks when hooked.... Would also be nice if we get hooked, but for some reason we decided to unhook and parked ourself, now i haven'T found a way to get msyelf off the shuttle once hooked.

Only way i've done some video shooting is by going in F4 or ALT-F4 view, can'T remember, and moving around the view with the numpad'S Slash, Star, - or +, can't remember without doing it, but explore this.

Thanks to GPS, Sattelites, technology and the Internet indeed. But you can add the details to precisiona step further. I was flying with a friend when map launched, we landed at , as i was in F11 view and moving around i was amazed to see there was a football/soccer field, i then told my friend about it and i found it funny.... The day after, he sent me a picture on Facebook of the soccer field i found, but, from Google Map, and pretty much looked like it and where it stands, exept in DCS, odd trees had grown in the middle of it. :P A few days after he flew with anotehr frind of us, which had been deployed in the areas, and told him it was so well done, he could spot an hotel he was at (building wasn't wel modeled of course cuz it's limited to building style generating) but the location of the building etc.. Here's a picture i've made to show the samll details of the Map, left Google Map and Right DCS.

Usualy Chuck does great guides, you shouyld grab it It's perfectly well explained there and most of the stuff we can get a « ? » over our heads, it'S a good reference when in question of basics stuff, very well done. https://forums.eagle.ru/showthread.php?t=212282 But to let people know on this threadinstead of clicking ona lit, to briefly point it out here; « Stores » drops the store/weappons only (Launchers/Racks remains). (IE: MK-82 drops but not the LAU's) « Rack/LHCR » Stores and their Launchers/Racks drops. (IE: MK-82 and LAU's drops)

If only Tracks wouldn't be Desync in 2.5.2 Open Beta.. though if we all provide tracks it might help the research about Tracks desync issue and finaly get fix so i can watch my replays doing carrier landings with my shinny Hornet ;)

Cool, but too late now, used the 3 seperate lines for each, but thanks.

Greetings, Haven't found traces of this with research, but, today i went another step on the Hornet learning lessons, the Waypoint management... So i wanted to add a Waypoint of a specific item's coordinates, like a vehicule, so i can test in conjunction with the Hornet's Auto bombing see how it handled... So i went in the F10 map vieux, click ont he vehicle to get it's coordinates, but on the lower left handed corner where info on the objet shows, i only get one part of the coordinates, the latitude and no longitude at all....? EDIT: Using 2.5.2.18521 Open Beta

Greetings guys, Tried to find answerd to my issue here, though i haven't passes mre than a few minutes to search. :) A few days ago i tried the Stingers Carrier mission, then stoped using it because there was an odd behaior on deck, which was anoying, the plane is sorta turning on itself/sliding as you try to taxi, i could also say it's kinda pivoting on it's own axis. On my missions it was all fine having a carrier miving at 20 kts, then yesterday i get to watch a video with a R/L Hornet Pilot/Ex Pilot, so i tried to set my carrier as he explained. So i set my Carrier according to him, between 25 and 30 kts, so made it 27 kts as he does his missions. Now bam, the issue occures, went in the Stingers mission, looked at it's speed, it'S at 30 kts.. so i presume this issue occurs somewhere 21 kts and 27 kts, since i was fine at 20 kts. Haven't found thread on this, unless it's an old issue reported back then? If anyone has this issue and found a way to counter it, mind to share? I guess i'll have to do test and find the exact speed it starts to behave like so.... EDIT: Forgot to mention, the effect is noticable after trapping, when the cable release and you try to taxi away. Applying wheel breaks and no throttle input and it still rotates even with cable not attached. Thanks

Fictionnal/Combination based on early 2003 CF-188933 Demo but using CF-188709 Demo Tail's fin arts.

I'm just curious man, no offence, but i can understand in RL this being useful etc.. but i wounder what would be the point of sitting in front of your computer and looking at a Virtual plane flying itself through waypoints? My personal fun is controling the aircraft.

Hey man! You had quite a few errors, i'll list you those if you were curious and below the working code you can copy/paste. Line 1- ackage.path = package.path ..';./Scripts/DemoScenes/?.lua;'Missing the « P » at package, first letter, first word. ----------------------------------------------------------------------------------- Lines 12, 39, 66 scene.m.setLivery = ("VFA-37", "FA-18C_hornet");Correct Syntaxe should be: scene.m:setLivery("VFA-37", "FA-18C_hornet");----------------------------------------------------------------------------------- Line 39: scene.m.setLivery = ("VFA-37", "FA-18C_hornet");It should be « scene.m2 » to match that scene 2 block. Line 66, same as line 39, it should be « scene.m3 » ----------------------------------------------------------------------------------- Line 67: scene.m3.transform:rotate(0,-90.0,0.0);I used instead: scene.m3.transform:setOrient(0,-90.0,0.0); ----------------------------------------------------------------------------------- Working Code: package.path = package.path ..';./Scripts/DemoScenes/?.lua;' local sceneEnvironment = require("demosceneEnvironment") scene = {} -- ???? ?????? ??? ????????? ??????? function loadScene(scenePtr) sceneAPI = sceneEnvironment.getInterface(scenePtr) sceneAPI:setUpdateFunc('sceneVRUpdate') sceneAPI:setSky(true); scene.m = sceneAPI:addModel("fa-18c", 0, 21.3, 0.0); scene.m:setLivery("VFA-37", "FA-18C_hornet"); scene.m:setArgument(0, 1); scene.m:setArgument(1, 0.7); scene.m:setArgument(3, 1); scene.m:setArgument(4, 0.8); scene.m:setArgument(5, 1); scene.m:setArgument(6, 0.8); scene.m:setArgument(8, 1.0); scene.m:setArgument(9, 0.6); scene.m:setArgument(10, 0.6); scene.m:setArgument(11, -0.4); scene.m:setArgument(12, -0.4); scene.m:setArgument(13, 1.0); scene.m:setArgument(14, 1.0); scene.m:setArgument(15, -0.5); scene.m:setArgument(16, -0.5); scene.m:setArgument(17, -0.8); scene.m:setArgument(18, 0.8); scene.m:setArgument(31, 0.1); scene.m:setArgument(32, 0.3); scene.m:setArgument(38, 0.9); scene.m:setArgument(50, 0.5); scene.m:setArgument(89, 1.0); scene.m:setArgument(90, 1.0); scene.m:setArgument(91, 1.0); scene.m2 = sceneAPI:addModel("fa-18c", 0, 21.3, 10.0); scene.m2:setLivery("VFA-37", "FA-18C_hornet"); scene.m2:setArgument(0, 1); scene.m2:setArgument(1, 0.7); scene.m2:setArgument(3, 1); scene.m2:setArgument(4, 0.8); scene.m2:setArgument(5, 1); scene.m2:setArgument(6, 0.8); scene.m2:setArgument(8, 1.0); scene.m2:setArgument(9, 0.6); scene.m2:setArgument(10, 0.6); scene.m2:setArgument(11, -0.4); scene.m2:setArgument(12, -0.4); scene.m2:setArgument(13, 1.0); scene.m2:setArgument(14, 1.0); scene.m2:setArgument(15, -0.5); scene.m2:setArgument(16, -0.5); scene.m2:setArgument(17, -0.8); scene.m2:setArgument(18, 0.8); scene.m2:setArgument(31, 0.1); scene.m2:setArgument(32, 0.2); scene.m2:setArgument(38, 0.9); scene.m2:setArgument(50, 0.0); scene.m2:setArgument(89, 1.0); scene.m2:setArgument(90, 1.0); scene.m2:setArgument(91, 1.0); scene.m3 = sceneAPI:addModel("fa-18c", 5.0, 21.3, -17.0); scene.m3:setLivery("VFA-37", "FA-18C_hornet"); scene.m3.transform:setOrient(0,-90.0,0.0); scene.m3:setArgument(0, 1); scene.m3:setArgument(1, 0.7); scene.m3:setArgument(3, 1); scene.m3:setArgument(4, 0.8); scene.m3:setArgument(5, 1); scene.m3:setArgument(6, 0.8); scene.m3:setArgument(8, 1.0); scene.m3:setArgument(9, 0.6); scene.m3:setArgument(10, 0.6); scene.m3:setArgument(11, -0.4); scene.m3:setArgument(12, -0.4); scene.m3:setArgument(13, 1.0); scene.m3:setArgument(14, 1.0); scene.m3:setArgument(15, -0.5); scene.m3:setArgument(16, -0.5); scene.m3:setArgument(17, -0.8); scene.m3:setArgument(18, 0.8); scene.m3:setArgument(31, 0.1); scene.m3:setArgument(32, 0.1); scene.m3:setArgument(38, 0.0); scene.m3:setArgument(50, 0.0); scene.m3:setArgument(89, 1.0); scene.m3:setArgument(90, 1.0); scene.m3:setArgument(91, 0.0); local cam_level = 21.2 scene.cam = sceneAPI:addCamera(3, cam_level , 2.5) scene.cam:setFov(90) scene.cam.transform:lookAtPoint(-10.0, cam_level, 5); scene.flr = sceneAPI:addModel("vinson", 20,0, -32.0); scene.flr:drawToEnvironment(true); --scene.flr.transform:scale(2,1.5,1.5); scene.flr.transform:rotate(0,-90.0,0.0); --[[ scene.sh = sceneAPI:addModel("ukrytie", 0,0,0); scene.sh:drawToEnvironment(true); scene.sh.transform:scale(2,2,2);]] scene.cam:setActive() end --[0;1] local function pingpong(length, t) local tt = (t%length)*2/length if tt>1 then tt = 2-tt end return tt end function sceneVRUpdate(t, dt) end

Wouln't do much, as all the stuff you replaced after the -- makes it just a note, adding -- before a line makes it a note/remarks.

Yeah thats what i thought so, but it seemed more transparent, i was hoping to. :)

Please, god no. That would make a dozen new lines in the description.lua file to replace the default texture to « EMPTY » on normal texture and specular/roughmat textures when creating a livery, that would be long and boring. :)

Thanks to SkateZilla for clearing out the use of livery setting syntaxe. Here's my updated VR Hangar Scene for thsoe who wants it, updated now to use the livery loading syntaxe, you can now edit each of the aricraft model to set your own liveries of the few F/A-18c Lot 20, the AV-8B and the M-2000C. https://www.digitalcombatsimulator.com/en/files/3300749/

Awesome thanks. iT's working now. :)

Will try this, if it works, i owe you a beer keg :P EDIT: Well, no Joy, i can't figure out how to use it. :(

Edited as June 8, 2018: Added to first post: 22- KC-135BDA - Fictional RCAF CC-150 Polaris grey skin 23- DCS 2.5.2 Open Beta - Hornet Hangar VR Menu Scene (RCAF CF-18's)

Updated it as 1.1 on Juine 7: Was finaly able to get rid of the remaining Digits showing up, no more bug « 0 », someone was finaly able to point me the proper Argument # which was wrong in the PDF Argument list i had. https://www.digitalcombatsimulator.com/en/files/3300749/

Updated as June 7 for 1.1: I was missing an Arguement # to hide de remaining number, so i had some 0 digits alll were digits should appear, someone finaly helped me out with the proper Argument # which was wrong fromt eh lsit i'Ve found. And made some load adjusments on Hornets. https://www.digitalcombatsimulator.com/en/files/3300749/

Pretty much complicated to explain, took me lots of analysing the .lua to understand etc, but basicly you jsut replace the shape used int he lua, though it's ugly and disgustin, cut what load is an infinite horizon like Modelviewer, with not really water, and the deck surface is limited, so it's fake and i find it immersion break down, i let the hangar walla to hide this crap stuff, even on mine with the door open you can see the crap floor going through the horizon but the menu and otehr hornets hides it. And as for the Carrier Hangar is low Res and ugly, so i tried to use an envrionement that is better resolution and hides the limitation of the VR scene.

No issues on 2.5 with the Harrier on Tarawa well the sorta 5 last replays i made to record videos. But haven't fly in there since 2.5.2 OB came out :)