BrassEm

I am trying to create a mission where all playable aircraft types are available and ready to jump into on mission start. I've placed all the aircraft as hot start from ramp so the user doesn't have to go through a start up procedure on the aircraft they enter. Trouble is they immediately start taxiing for take off on mission start no matter what scripting I use to try and disable the AI or stop the group. This is for version 2.1.1 to showcase the new maps with Oculus Rift. Is there a working solution?

Thanks SkateZilla, I was not aware of that. I will check to see if the directories are deleted during a repair. Update; Just did a repair and the files remained so all good.

Is that the ED prefered directory SkateZilla? The \DCS World\Bazar\Liveries\B-17G\ is working for me?

G'day Keith, I have just added links to some of my B-17G skins which may be a guide here If you are still having troubles let us know. Cheers,

I was able to confirm that this works. You will need to change the third column names to your textures. Pathway: \Bazar\Liveries\B-17G\B-17G Your Livery Subject to change of course!!! -- B-17G 8th Air Force. 381st Bomber Group, 532nd Bomber Squadron. USAAF England 1944. -- Skin by BrassEm -- Version 1.0 20170627 livery = { {"B17G_Fuzelage_1", 0 ,"B-17G_Fuzelage_1_D",false}; {"B17G_Fuzelage_1", 1 ,"B-17G_Fuzelage_1_N",true}; {"B17G_Fuzelage_1", 2 ,"B-17G_Fuzelage_1_S",false}; {"B17G_Fuzelage_2", 0 ,"B-17G_Fuzelage_2_D",false}; {"B17G_Fuzelage_2", 1 ,"B-17G_Fuzelage_2_N",true}; {"B17G_Fuzelage_2", 2 ,"B-17G_Fuzelage_2_S",false}; {"B17G_Wing_Left", 0 ,"B-17G_Wing_Left_D",false}; {"B17G_Wing_Left", 1 ,"B-17G_Wing_Left_N",true}; {"B17G_Wing_Left", 2 ,"B-17G_Wing_Left_S",false}; {"B17G_Wing_Right", 0 ,"B-17G_Wing_Rigth_D",false}; {"B17G_Wing_Right", 1 ,"B-17G_Wing_Rigth_N",true}; {"B17G_Wing_Right", 2 ,"B-17G_Wing_Rigth_S",false}; } name = "8thAF, 381st BG, 532nd BS, VE-N" countries = {"USA", } I do hope ED brings out a template for it. It is an outstanding model with superb attention to detail. Cheers,

The good news is that it was pretty straight forward to create the description.lua from the model.edm. It works in mission editor so there can be multiple liveries. I need to increase the size of the fuselage "Stars and Bars" for this livery. Once that is done I will post a link to download it on my first post. Hopefully by next weekend. Cheers,

Thank you Gentlemen. Everytime I see these in game my eyes keep popping. (Happens when flying in DCS full-stop these days!) ED have done a truly outstanding job with all their modelling and texturing. It is unsurpassed. As it stands now I have to over-write the original wing and fuselage .dds's. I am trying to work out the description.lua so that many Liveries can be added. I am sure the coding will come later but it would be good to see these in game now. If I don't have any success soon then I will upload them as is.

UPDATE: Sunday 16th July 2017 Learning the nuances of the new template and specular mapping. I hope to post better "metalised" liveries soon. (I cannot thank Eagle Dynamics enough for releasing a template!) UPDATE: Sunday 9th July 2017 Replaced previous links and added a link to download a single zip file containing Part 1 of the 352nd Squadron Liveries, (More to come). This is for a flight of VE-F,K,N,O (Minus nose art), plus the blank, and default description.lua to keep the default livery in Mission Editor. When extracting please use "Extract Here" for individual folders. These are an improved version on the original post. I cannot implore ED enough to release templates. Even a default plain (UnSquadroned) Olive Green/Drab, and an Aluminium livery would be great. Working with the textures you really get to appreciate what outstanding models Eagle Dynamics create, with the fine texturing and superb attention to detail. These are great days. Link is below; (Subject to change!) IMPORTANT: If you add these skins you will need to add the description.lua for the default skin in Mission Editor. B-17G_8thAF_381stBG_Part1_v101_by_BrassEm.zip Cheers,

Thanks Strut. I guess I should upload these as is anyways. I am sure there are a lot of improvements that could be made on them.

Excellent work there Strut. A complete texture of both aircraft and pilot is brilliant. Looking forward to flying them.

It is only a temporary fix as stated above. Are you refering to Type C roundels? Any issues can be properly addressed if and when we get a template. (As well as being able to do full profiles.)

Now that Normandy is out the D-Day Standard Texture needs fixing (No. 126 Squadron). See the first post for the link to the fixed texture.

Glad you got it sorted. A clean install will do it, but as you say, it is a real pain. (And not always an option).

Sorry to hear that you are still having troubles Wilbur81. I was without my X-55 for a few months a while back when a driver corrupted in Windows 7. The throttle would not work. I tried everthing I knew to get it back to no avail. Tech support did not have a clue how to fix it. I even bought a second set to try for a fix. (This is now attached to an arduino MEGA interface :) ) I did eventually stumble across the fix through a mountain of trial and error. The fix is not for the faint hearted. It does require editing the registry, if you make a mistake in there it is usually terminal, requiring a full reload of the operating system. You need to flush out all reference to the x-55. All x-55 drivers and references to them in the operating system have to be deleted. Then you have to manually add the drivers to the operating system via MSDOS commands, not autoinstall as it buggers it up. When you plugh the x-55 back in it does work. If you feel confident that you can handle the process then PM me for the details. I don't want to publish registry editing details publicly as it has catastrophic results if not done correctly.

@ Wilbur81, Can you revert back to a previous restore point prior to the update? I've found this can help sometimes when things goes pear-shaped

Only some very minor details need to be adjusted. Otherwise good to go. Will revisit. Update 24/06/2017 On checking my files on the old data disk drive I've discovered that the directory has corrupted and is unreadable. The skins are what they are with no chance of updating them unless I do them from scratch again, which will be low on the list.

Cookin up a storm for sure! :thumbup:

Brilliant find there Frusheen! (And of course FSF_Ian!) (Kudos on the killer PC too.) Also the new Export.lua that vJaBoG32 posted is perfect as it shows the matrix code for resultant vectors with applied rotation and scalars. Much test flying ahead.

Does the dot show up on your desktop screen as well?

Great work MetalGear! I've ordered some Teensy's and looking forward to trying out your code as well. I've got the motor hardware breadboarded ready for testing.

Matrix33() function errors when put into export.lua. (Not implimented yet or I've used incorrect syntax?). I get a dsc.log entry of; 00256.044 ERROR Lua::Config: Call error LuaExportAfterNextFrame:[string "C:\Users\Dave\Saved Games\DCS\Scripts\Export.lua"]:75: attempt to call global 'Matrix33' (a nil value) stack traceback: [C]: in function 'Matrix33' [string "C:\Users\Dave\Saved Games\DCS\Scripts\Export.lua"]:75: in function <[string "C:\Users\Dave\Saved Games\DCS\Scripts\Export.lua"]:45>. The function LoGetSelfData() data.Heading, data.Pitch, data.Bank returns the same values as the LoGetADIPitchBankYaw() function.

WOW! Top notch work there Matbog. Keep the updates coming.

Grats on an absolutely brilliant build TR. I am sure you have found that there is never enough time now. You do however have me intrigued. Would you be kind enough to post a video of you doing vertical loops please. I would be most interested to see how your rig handles the 180° loop flip from DCS World. The software I use does not handle this inversion properly at all. I would be very very interested to see how your software behaves. Thanks.

Thanks for the heads-up! Looks like I will be skinning some zeroes as well :) (Many thanks Markindels for making this possible.) Thanks VH-Rock! Lots of pixel pushing, load and re-loads. But worth it. .

Wow! Excellent work. Keep it coming.