Captain Orso Posted April 22, 2019 Posted April 22, 2019 I'm not able to make it work please could you put an example with the fa/18 and in which folders you have the custom skin? thank you. You have to put your custom skins under '..\Eagle Dynamics\DCS World\Bazar\Liveries\'. If ME and ModelViewer2 can find them, you should be okay. When you hit the wrong button on take-off System Specs. Spoiler System board: MSI X670E ACE Memory: 64GB DDR5-6000 G.Skill Ripjaw System disk: Crucial P5 M.2 2TB CPU: AMD Ryzen 7 7800X3D PSU: Corsair HX1200 PSU Monitor: ASUS MG279Q, 27" CPU cooling: Noctua NH-D15S Graphics card: MSI RTX 3090Ti SuprimX VR: Oculus Rift CV1
Ala12Rv-Muscat Posted April 22, 2019 Posted April 22, 2019 I'm not able to make it work please could you put an example with the fa/18 and in which folders you have the custom skin? thank you. another question....the hornet model for the vt hangar is the new hornet model or the older one? Thank you! _______________________________________
Ala12Rv-Muscat Posted April 22, 2019 Posted April 22, 2019 (edited) You have to put your custom skins under '..\Eagle Dynamics\DCS World\Bazar\Liveries\'. If ME and ModelViewer2 can find them, you should be okay. yes Modelviewer2 can find and read my custom skin but i confuse with the line code: scene.m1:setLivery("485th FS", "P-51D-25-NA"); my skin name its "dani" so how should I write this line? scene.m1:setLivery("dani" , "f-18c"); ?? these are the two lines of code that I have added to sceneVR.lua but, at the moment the default vfa-94 skin appears scene.m = sceneAPI:addModel("f-18c", 0, 2.4, 0); scene.m:setLivery("dani" , "f-18c"); thank again buddy Edited April 22, 2019 by Muscat _______________________________________
Captain Orso Posted April 22, 2019 Posted April 22, 2019 yes Modelviewer2 can find and read my custom skin but i confuse with the line code: scene.m1:setLivery("485th FS", "P-51D-25-NA"); my skin name its "dani" so how should I write this line? scene.m1:setLivery("dani" , "f-18c"); ?? these are the two lines of code that I have added to sceneVR.lua but, at the moment the default vfa-94 skin appears scene.m = sceneAPI:addModel("f-18c", 0, 2.4, 0); scene.m:setLivery("dani" , "f-18c"); thank again buddy Yeah, I can't get any of this to work either. I've given up. IIRC Skate mentioned somewhere that the aircraft name has to be the folder name, but I find at least two possible folder names for the F-18, f_a-18c, and FA-18C_hornet. You'll have to look around and see what folder names you can find; maybe they all work, but the skin must be inside. IDK. ED could have had such a neat thing that could have been a nice community gathering point, kind of like collecting and trading cards, only you can make your own. I'm not going to rant or curse or carry on. It'll only get me banned and do no good. Apparently ED sees no reason to commit resources to fix and support this at this time. From my experience, anything I say from this point on is pointless, so I'll not do that. Sorry. When you hit the wrong button on take-off System Specs. Spoiler System board: MSI X670E ACE Memory: 64GB DDR5-6000 G.Skill Ripjaw System disk: Crucial P5 M.2 2TB CPU: AMD Ryzen 7 7800X3D PSU: Corsair HX1200 PSU Monitor: ASUS MG279Q, 27" CPU cooling: Noctua NH-D15S Graphics card: MSI RTX 3090Ti SuprimX VR: Oculus Rift CV1
Ala12Rv-Muscat Posted April 22, 2019 Posted April 22, 2019 ok buddy, thanks anyway! _______________________________________
Nealius Posted May 2, 2019 Posted May 2, 2019 (edited) Is anyone having issues with the setLivery command? It used to work fine but now it won't work for any aircraft, even if I copy/paste the livery name directly from the description.lua file. And yes, they are liveries from inside the main DCS install. NOT from Saved Games. The "sceneAPI:setSky(true);" is also not working. I just get a black sky. Edited May 2, 2019 by Nealius
Nealius Posted May 3, 2019 Posted May 3, 2019 Okay, figured out my problems. Now I have a new problem. Adding a second aircraft model causes DCS to crash before loading the VR menu. Here's the code I have: scene.m = sceneAPI:addModel("f-14b", -1.0, 0.5, 4); scene.m:setLivery("VF-143 Pukin Dogs CAG", "F-14B"); scene.m.transform:setOrient(0,270,0); scene.m:setArgument(0, 1); --nose gear scene.m:setArgument(3, 1); --left gear scene.m:setArgument(5, 1); --right gear scene.m:setArgument(4, 0.25); scene.m:setArgument(6, 0.25); scene.m:setArgument(115, 1); scene.m:setArgument(116, 1); scene.m:setArgument(117, 1); scene.m:setArgument(7, 0); --wing sweep scene.m:setArgument(8, 1); --wings folded scene.m:setArgument(38, 0.9); --canopy scene.m2 = sceneAPI:addModel("fa-18c", -1.0, 0.5 12); scene.m2:setLivery("VFA-131", "FA-18C_hornet"); scene.m2:transform:setOrient(0,270,0); scene.m2:setArgument(0, 1); --nosegear scene.m2:setArgument(3, 1); --left gear scene.m2:setArgument(5, 1); --right gear scene.m2:setArgument(4, 0.25); scene.m2:setArgument(6, 0.25); scene.m2:setArgument(115, 1); scene.m2:setArgument(116, 1); scene.m2:setArgument(117, 1); scene.m2:setArgument(8, 1); --wings folded scene.m2:setArgument(38, 0.9); --canopy If I remove the scene.m2 entries it fixes the crash, but I don't understand why it's causing a crash in the first place. Everyone else's VR hangars have the same scene.m2 syntax, and theirs works fine.
Tailhook Posted May 5, 2019 Posted May 5, 2019 (edited) Shouldn't be a ; at the end of the main API commands sceneAPI:setSky(true) sceneAPI:setCirrus(true) If I remove the scene.m2 entries it fixes the crash, but I don't understand why it's causing a crash in the first place. Everyone else's VR hangars have the same scene.m2 syntax, and theirs works fine. m means nothing. It is just a name variable and can use anything. You could use f14, tomcat, tcat, etc. You missed a , and : instead of . scene.m = sceneAPI:addModel("f-14b", -1.0, 0.5, 4); scene.m.transform:setOrient(0, 270, 0); scene.m:setLivery("VF-143 Pukin Dogs CAG", "f-14b"); scene.m:setArgument(0, 1); scene.m:setArgument(3, 1); scene.m:setArgument(5, 1); scene.m:setArgument(4, 0.25); scene.m:setArgument(6, 0.25); scene.m:setArgument(115, 1); scene.m:setArgument(116, 1); scene.m:setArgument(117, 1); scene.m:setArgument(7, 0); scene.m:setArgument(8, 1); scene.m:setArgument(38, 0.9); scene.m:drawToEnvironment(true); scene.m2 = sceneAPI:addModel("fa-18c", -1.0, 0.5, 12); scene.m2.transform:setOrient(0, 270, 0); scene.m2:setLivery("VFA-131", "FA-18C_hornet"); scene.m2:setArgument(0, 1); scene.m2:setArgument(3, 1); scene.m2:setArgument(5, 1); scene.m2:setArgument(4, 0.25); scene.m2:setArgument(6, 0.25); scene.m2:setArgument(115, 1); scene.m2:setArgument(116, 1); scene.m2:setArgument(117, 1); scene.m2:setArgument(8, 1); scene.m2:setArgument(38, 0.9); scene.m2:drawToEnvironment(true);For a cleaner code example than a bunch of posts on the forum, see my post from a few months ago - https://forums.eagle.ru/showpost.php?p=3659691&postcount=55 Edited May 5, 2019 by Tailhook Intel i9-13900K : ASUS TUF RTX 4080 : 32GB G.Skill RipjawsV 4000 : TM HOTAS Warthog : HP Reverb G2
Nealius Posted May 5, 2019 Posted May 5, 2019 Ugh, typos are going to be the death of me. It's often faster just to rewrite everything instead of hunt for a period instead of a colon when everything blends into a mess that all looks the same to your brain.
Tailhook Posted May 5, 2019 Posted May 5, 2019 Ugh, typos are going to be the death of me. Use a proper code editor like Notepad++. It's color-coding helps identify typos. https://notepad-plus-plus.org/download/v7.6.6.html Intel i9-13900K : ASUS TUF RTX 4080 : 32GB G.Skill RipjawsV 4000 : TM HOTAS Warthog : HP Reverb G2
FlyBoyd Posted May 20, 2019 Posted May 20, 2019 Gents, I'm having some issues with the F-14 in the hanger. I got it in there just fine, but I noticed the right main landing gear is in the up position (however the gear doors are open). Here is my code: scene.m = sceneAPI:addModel("f-14b", 0, 2.15, 0); scene.m:setArgument(0, 1); scene.m:setArgument(3, 0.25); scene.m:setArgument(5, 1); scene.m:setArgument(4, 0.25); scene.m:setArgument(6, 0.25); scene.m:setArgument(115, 1); scene.m:setArgument(116, 1); scene.m:setArgument(117, 1); local cam_level = 1.8 scene.cam = sceneAPI:addCamera(3, cam_level , 3) scene.cam:setFarClip(1000.0) scene.cam:setFov(90) scene.cam.transform:lookAtPoint(-10.0, cam_level, 0); I also noticed that the f-14 nose gear appears to be raised off the ground when the main gear aren't. Any ideas? Thanks Intel I9-9900k, Gigabyte AORUS Ultra, 64GB G.SKILL Trident Z Royal 3200, EVGA 2080Ti, Samsung M.2 960 Pro 512, Samsung M.2 960 Pro 1TB, MCG, Vipril, TM Controls, SLAW device rudders, Obutto Revolution, Valve Index
Nealius Posted May 20, 2019 Posted May 20, 2019 (edited) scene.m:setArgument(3, 0.25); That would partially extend the right main gear. The second value 0 is full up, 1 is full down. Probably explains why the gear doors are open but the gear looks retracted. For the nose strut, try playing with the nose-strut compression argument: setArgument(1, 0), where the second value of 0 is fully uncompressed, 1 compressed, and fractions would be partial compression. If anyone needs help, you can find general arguments for most DCS modules in this PDF file (found somewhere here on the forums, don't know who authored it for credit). More arguments for the F-14, like flaps, hook, pilot/RIO head positions, wing sweep, etc. can be found in Mods/Aircraft/F14/Cockpit "draw_args.lua" Edited May 20, 2019 by Nealius 1
FlyBoyd Posted May 21, 2019 Posted May 21, 2019 That would partially extend the right main gear. The second value 0 is full up, 1 is full down. Probably explains why the gear doors are open but the gear looks retracted. For the nose strut, try playing with the nose-strut compression argument: setArgument(1, 0), where the second value of 0 is fully uncompressed, 1 compressed, and fractions would be partial compression. I changed that .25 back to a 1 and it didn't change anything. I thought that was for the main gear. Intel I9-9900k, Gigabyte AORUS Ultra, 64GB G.SKILL Trident Z Royal 3200, EVGA 2080Ti, Samsung M.2 960 Pro 512, Samsung M.2 960 Pro 1TB, MCG, Vipril, TM Controls, SLAW device rudders, Obutto Revolution, Valve Index
Nealius Posted May 21, 2019 Posted May 21, 2019 I could have gotten my left/right main gear arguments mixed up. Argument three is one of the main gear. Best to check that PDF to make sure which is right and which is left.
rogonaut Posted October 11, 2019 Posted October 11, 2019 (edited) i didnt find any FW-190D9 edm besides the pilot? nevermind found it :D Edited October 11, 2019 by rogonaut
sirrah Posted January 2, 2020 Posted January 2, 2020 (edited) Did anyone here perhaps create a "sceneVR.lua" for the Viper? And would he/she be so kind and share it with me (us)? :worthy: Would love to see one on the tarmac under the Persian Gulf sun, but I have no idea how to do that. Edited January 2, 2020 by sirrah System specs: i7-8700K @stock speed - GTX 1080TI @ stock speed - AsRock Extreme4 Z370 - 32GB DDR4 @3GHz- 500GB SSD - 2TB nvme - 650W PSU HP Reverb G1 v2 - Saitek Pro pedals - TM Warthog HOTAS - TM F/A-18 Grip - TM Cougar HOTAS (NN-Dan mod) & (throttle standalone mod) - VIRPIL VPC Rotor TCS Plus with ALPHA-L grip - Pointctrl & aux banks <-- must have for VR users!! - Andre's SimShaker Jetpad - Fully adjustable DIY playseat - VA+VAICOM - Realsimulator FSSB-R3 ~ That nuke might not have been the best of ideas, Sir... the enemy is furious ~ GUMMBAH
Gnadentod Posted January 25, 2020 Posted January 25, 2020 Very basic VR hangar, plane replaced with the F16. File goes to "\DCS World\Scripts\DemoScenes\sceneVR.lua" If there's a higher quality model available feel free to chat up.sceneVR.lua
sirrah Posted January 26, 2020 Posted January 26, 2020 Very basic VR hangar, plane replaced with the F16. File goes to "\DCS World\Scripts\DemoScenes\sceneVR.lua" If there's a higher quality model available feel free to chat up. Thanks for your effort Hirte This however appears to be the default AI model of the F-16, not the DLC model. Does anyone know what name I should type to see the DLC model? = sceneAPI:addModel("f-16", 0, 1.7, 0); I tried several things (e.g. F-16C, F-16CM, F-16-50, F-16-bl50, etc.) but couldn't find the correct one System specs: i7-8700K @stock speed - GTX 1080TI @ stock speed - AsRock Extreme4 Z370 - 32GB DDR4 @3GHz- 500GB SSD - 2TB nvme - 650W PSU HP Reverb G1 v2 - Saitek Pro pedals - TM Warthog HOTAS - TM F/A-18 Grip - TM Cougar HOTAS (NN-Dan mod) & (throttle standalone mod) - VIRPIL VPC Rotor TCS Plus with ALPHA-L grip - Pointctrl & aux banks <-- must have for VR users!! - Andre's SimShaker Jetpad - Fully adjustable DIY playseat - VA+VAICOM - Realsimulator FSSB-R3 ~ That nuke might not have been the best of ideas, Sir... the enemy is furious ~ GUMMBAH
Gnadentod Posted January 27, 2020 Posted January 27, 2020 I know and I tried some variations aswell but didn't bother after a few tries, I'm inside the hangar for only 15 seconds per use.
sirrah Posted January 27, 2020 Posted January 27, 2020 I know and I tried some variations aswell but didn't bother after a few tries, I'm inside the hangar for only 15 seconds per use. I know I know, and I also just tried for a few minutes Not a big deal obviously, but still, it would be a nice detail to have :) System specs: i7-8700K @stock speed - GTX 1080TI @ stock speed - AsRock Extreme4 Z370 - 32GB DDR4 @3GHz- 500GB SSD - 2TB nvme - 650W PSU HP Reverb G1 v2 - Saitek Pro pedals - TM Warthog HOTAS - TM F/A-18 Grip - TM Cougar HOTAS (NN-Dan mod) & (throttle standalone mod) - VIRPIL VPC Rotor TCS Plus with ALPHA-L grip - Pointctrl & aux banks <-- must have for VR users!! - Andre's SimShaker Jetpad - Fully adjustable DIY playseat - VA+VAICOM - Realsimulator FSSB-R3 ~ That nuke might not have been the best of ideas, Sir... the enemy is furious ~ GUMMBAH
pimp Posted January 30, 2020 Posted January 30, 2020 ...I tried several things (e.g. F-16C, F-16CM, F-16-50, F-16-bl50, etc.) but couldn't find the correct one I believe it should be "f-16c_bl50" since that's the name of the .edm file for the new Viper. i9 14900k @5.6GHz NZXT Kraken |Asus ROG Strix Z790 A-Gaming | Samsung NVMe m.2 990 Pro 2TB | 64GB DDR5 6400MHz EVGA RTX 3090 FTW3 Ultra | PiMAX CRYSTAL LIGHT | HOTAS Warthog | Saitek Flight Pedals
Screamer63 Posted April 3, 2020 Posted April 3, 2020 Oh for the Love of God!!!! I have been working on a VR Viper menu for a day now had it working with my squadron skin.. :) But had to go in and tweak some stuff now NOTHING... and No I don't remember what I did.. lol Can someone PLEASE post a Viper VR Menu with the Newest model??? It was Real late in the morning and sleepy but couldn't stop until I had it working then FUBARED IT!! Cant remember what and where all the files were at... TIA!! Screamer
sirrah Posted April 3, 2020 Posted April 3, 2020 Oh for the Love of God!!!! I have been working on a VR Viper menu for a day now had it working with my squadron skin.. :) But had to go in and tweak some stuff now NOTHING... and No I don't remember what I did.. lol Can someone PLEASE post a Viper VR Menu with the Newest model??? It was Real late in the morning and sleepy but couldn't stop until I had it working then FUBARED IT!! Cant remember what and where all the files were at... TIA!! Screamer It's pretty easy to do (I did it too for the viper a while ago, but I can't sent it to you as the file has been overwritten since one of the patches) Just go to your \DCS World\Scripts\DemoScenes\sceneVR.lua folder, open the lua file with notepad and change su-27 in f-16c_bl50 In that same lua, you might have to slightly alter the coordinates, to place the viper a little lower so that its wheels touch the ground System specs: i7-8700K @stock speed - GTX 1080TI @ stock speed - AsRock Extreme4 Z370 - 32GB DDR4 @3GHz- 500GB SSD - 2TB nvme - 650W PSU HP Reverb G1 v2 - Saitek Pro pedals - TM Warthog HOTAS - TM F/A-18 Grip - TM Cougar HOTAS (NN-Dan mod) & (throttle standalone mod) - VIRPIL VPC Rotor TCS Plus with ALPHA-L grip - Pointctrl & aux banks <-- must have for VR users!! - Andre's SimShaker Jetpad - Fully adjustable DIY playseat - VA+VAICOM - Realsimulator FSSB-R3 ~ That nuke might not have been the best of ideas, Sir... the enemy is furious ~ GUMMBAH
Screamer63 Posted April 7, 2020 Posted April 7, 2020 (edited) It's pretty easy to do (I did it too for the viper a while ago, but I can't sent it to you as the file has been overwritten since one of the patches) Just go to your \DCS World\Scripts\DemoScenes\sceneVR.lua folder, open the lua file with notepad and change su-27 in f-16c_bl50 In that same lua, you might have to slightly alter the coordinates, to place the viper a little lower so that its wheels touch the ground So here is the Final Completed WORKING F-16C VR MENU Script.. I have it just how I want it for the F-16C with my Squadron skin but I can't figure out why the lights wont work?? Anyone have them working and share How you did it? LOL TIA.. It is my squadron skin location but you get the idea... :) ENJOY.. package.path = package.path ..';./Scripts/DemoScenes/?.lua;' local sceneEnvironment = require("demosceneEnvironment") scene = {} -- сюда кладем все созданные объекты function loadScene(scenePtr) sceneAPI = sceneEnvironment.getInterface(scenePtr) sceneAPI:setUpdateFunc('sceneVRUpdate') sceneAPI:setEnvironmentMap("Bazar/Graphics/VRMainScene.dds",0.9); sceneAPI:setSun(math.rad(-90), math.rad(0)) -- сажаем солнце за горизонт чтоб не светило scene.m = sceneAPI:addModel("f-16c_bl50", -2.0, 2.0, 6.5); scene.m:setLivery("51st FW-36FS - 89-020", "f-16c_50"); scene.m:setArgument(0, 1); scene.m:setArgument(3, 1); scene.m:setArgument(5, 1); scene.m:setArgument(4, 0.25); scene.m:setArgument(6, 0.25); scene.m:setArgument(115, 1); scene.m:setArgument(116, 1); scene.m:setArgument(117, 1); scene.m:setArgument(38, 0.7); -- Canopy OPEN/CLOSED scene.m:setArgument(184, 1); -- Speed Brakes scene.m:setArgument(191, 0.5); -- Nav Lights scene.m:setArgument(192, 0.5); -- Strobe Lights scene.m:setArgument(190, 0.5); -- Formation Lights scene.m:setArgument(208, 0.9); -- TAXI Lights 1 scene.m:setArgument(209, 1); -- TAXI Lights 2 scene.m:setArgument(210, 1); -- TAXI Lights 3 local cam_level = 1.8 scene.cam = sceneAPI:addCamera(3, cam_level , 3) scene.cam:setFarClip(1000.0) scene.cam:setFov(90) scene.cam.transform:lookAtPoint(-10.0, cam_level, 0); scene.flr = sceneAPI:addModel("shelter_floor", 0,0,0); scene.flr:drawToEnvironment(true); scene.flr.transform:scale(2,1.5,1.5); scene.sh = sceneAPI:addModel("ukrytie", 0,0,0); scene.sh:drawToEnvironment(true); scene.sh.transform:scale(2,2,2); scene.L1 = sceneAPI:addLightOmni(0, 25, 0, 1,0.8,0.5); scene.L1:setRadius(200); scene.L1:setAmount(1); 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 Edited April 8, 2020 by Screamer63
DayGlow Posted May 20, 2020 Posted May 20, 2020 hoping someone smarter than me can make a new supercarrier hanger screen "It takes a big man to admit he is wrong...I'm not a big man" Chevy Chase, Fletch Lives 5800X3D - 64gb ram - RTX3080 - Windows 11
Recommended Posts