BrassEm

If you can afford it, I would do it. It really does put you inside the 3d pit. You will never be able to explain it until you have tried it. Don't expect crystal clear images like a 2d monitor though (at least not yet). It depends on whether you want to be IN the pit IN the simulation, but with some blur, or value a sharp image looking at a 2d monitor in the room your in. Head and hand tracking is excellent (Oculus touch). Virtual hand switching is not implemented yet though. HOTAS does that for you at the moment. The only issue I have with my setup is object stutter when low down and looking at complex terrain objects left or right out of the cockpit. Head on is okay. (Mid range PC.) Plus you get the VR experience with other software titles as well. (Then try it with a g-Seat!!!)

No worries mate! I can understand that. I love every minute I work on those liveries.

UPDATE: Wednesday, 19th July, 2017. Opening the template with Photoshop CS4 64bit is broken. It cannot handle the format (obviously the template is a later version => CS6.) Missing a whole lot of mechanicals and diffused layers. It is workable, and I am very thankful for that, but it is going to take a very long time to drop in pixels to get the template into a useable format. At this rate I dont expect to push liveries for a few months yet.

I am getting a dialog box when I try to open the template .psb (Large Format Document). When I click Flatten it flattens the file to the default diffused texture of the default livery. If I click keep layers a new dialog box comes up; "Some groups were found corrupted and repaired." and I click ok. Photoshop opens the file with a huge array of layers for the diffused, normal and specular maps. If I flatten straight after loading all being well I should get the default livery as per the original flatten option. I don't get the flatten default livery meaning that I am missing layers. Looking at the diffused layer I cannot see the main livery. (On opening I have 26 diffused layers). Has anyone opened the file successfully? This may not be a show stopper as it looks as though all the other technical layers are intact. Apart from that... I must give Eagle Dynamics and the artists involved a huge thank you for very kindly releasing their template. Now there is never enough hours in the day... :thumbup:

Yeah, I think I may have altered the original specular mapping tint a little while doing some editing. (First time editing spec maps). Now that we have the template it might be easier to edit. I will look into it. Hopefully it will be a matter of just posting new specular files. UPDATE: It is not the specular maps but the aluminium gray shade is way too dark in the diffused. Fixing now and reposting version 1.02 when done. Much Better.

Updated Liveries for a flight of VE-F,K,N,O. See first post for download. Cheers,

Numeric 5 to recenter view. Click and hold middle mouse button and scroll back with it two or three "positions" to pull back eye view postion while in cockpit. (Scroll forward to move eye point forward.)

Thanks fee, that worked great. (Rep inbound!).

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: