352ndDeacon

A skining guide sure would help a lot of us and take pressure off those who keep getting requests for individual skins. There are templates out there, especially for the P51, but without the step by step guide they are useless. Please help us!

I currently have two ssd's, one for my OS( win7 home) and another on which I have DCS 1.5.6 and 2.0.5 along with all modules. I will be installing another, larger, ssd to take the place of the one which has my OS on it. I will be putting win 10 pro on the new one along with whatever was on the old one. I will also be increasing my RAM from 16 to 32 gigs. The ssd which has DCS will remain untouched. My question is this: since DCS is on the untouched ssd, will I still need to deactivate before I make hardware changes and then after the changes, activate DCS and all the modules again?

Clicking on the links given in response #5 does not give you a link to driver 6.0.4.1 or SST 6.6.6.9. It connects you an ftp site that gives the latest drivers and SST software. Where can we get the drivers mentioned in response #5, the 6.0.4.1 and 6.6.6.9?

If we have contributed to the Kickstarter with enough $ and on our profile page we know we will be getting the map along with the asset pack for free, what do we need to do now? Do we still sign up for pre-purchase? Or after the Normandy release, if we go into the module manager to d/l, does it recognize us as getting it for free? Do we still need to install the VC runtime 14?

We need to d/l that new runtime for the Nevada map update. But will we need that also for the Normandy map? Or will it run like 1.5.6 which doesn't need it? So to summarize, will the new runtime be needed for the Normandy map?

Repair didn't fix mine. I have NO mods activated and clicking on the red shield show the following: Mods/aircraft/c_130/dcs_manifest.x86_64 Checked the folder for Mods/aircraft/c_130 and there is no file "dcs_manifest.86_64 I just did the repair again and there still is no such file. Any suggestions?

Thanks DavidRed. I'll try it tomorrow since I still have 1.5.5

Wags, If southern England is going to have less detail, will the "grass airfield" static object allow us to make an airfield wherever we can find a level area? and if so, will we be able to spawn planes and take off and land on those airfields?

Is there any further news if this is working? I'd like to make a grass infield but can't seem to spawn any planes on it.

Can you have one module ( say a 109) with one type of joystick which is not ffb and another (TF51) which is?

If the host of a mp mission has WWII German mods installed so that certain objects or vehicles are within the mission, does a player, who enters the mp and not have these mods installed, see them and can they destroy them? Also with the same scenario, if plane mods are installed on the host machine, can players, who do not have these plane mods installed, see and destroy these planes?

Same problem with my X52 and Saitek rudder pedals.

I currently have DCS along with combined arms, P51D Mustang and the FW190 installed on my computer. I am building a new computer which will be a great update from what I have with new SSD's. My question is, - What is the proper way to install everything for DCS that I have right now on the new computer. I have all the serial numbers for all my modules but want to install it properly so I won't have any problems once I try to fly on the new computer. Thanks in advance for the info.

Where is the steel mesh runway located? In static objects?

I found the solution and it was to set the DCS world icon on the desktop to "run as administrator" and everything worked.

After updating to 1.2.8 (not the beta but the actual release of 1.2.8) DCS will not allow me to launch any of the training saved missions of connect to multiplayer. The log says that there is an error code of dcs.exe failed error code 740. Any help would be appreciated. I am running windows 7 x64 and have 8 gigs of ram. Dxdiag shows no problems and DCS was running fine with 1.2.7

DCS A-10C Warthog, please and thank you for the offer. Merry Christmas to all on the forum and especially you.

Just and update to the problem which is now corrected. While I still had my router (Netgear) connected originally and had the ports opened, when Comcast installed my new gateway modem, I was informed that the router in that modem would not be activated. But it was and needed to have the 10308 port opened. In addition, my antivirus also also needed to allow TCP and UDP going to that port. Once that was corrected, my server appeared and my squad mates could enter it at will.

Eno, I did all that you suggested but still a no go. The sad thing about it is that others in my squad who had servers up and running before the latest auto update, also can't get their games to show on the server list and we can't connect to each other's servers. All games are authenticated and have the latest update. Nothing has changed on any of our ends. the only change has been the latest update. I did the repair but still no help. I renamed the DCS folder - no help. The 10308 port was opened and checked - no go. We don't understand it but it seems that many others have the same problem. We can connect the the servers that are listed. If any of you who have servers up and running that we can connect with, can offer any suggestions for what you might have done, it would be appreciated.

Abburo, thanks for the info. Now can you give us non technical computer novices a step by step to fix the problem? Thank you in advance.

Did anyone figure out what is causing this problem? My entire group is having the same issue since the latest update and none of us have changed anything on our machines since before the update. We can connect and fly in any of the servers that are set up already but we cannot set up our own server and either see it or connect directly to the ip. We were able to do so before the latest update.

Not to argue the point that the plane you saw at the air show has noseart on both sides, having spent many hours with the pilots of the 352ndFG and having copies of their books, "The Bluenosed Bastards of Bodney" and "Bluenoser Tales", both of which contain hundreds of pictures taken by the pilots and ground crews of the actual P-51's flown in WWII, I have seen none with noseart on both sides. If they were flown by more than one pilot and the secondary pilot wished noseart, then it was painted on the right side according to the list of planes in the "Bluenosed Bastards of Bodney". These were only a few in number and I am currently looking for your plane, which would have been flown within the 487th FS according to the color of the rudder. The skin you made is beautiful and if that's the way you want it, great! It's your creation and congratulations on your talent and effort.

Also the noseart was only on the plane's left side and the tail color being blue means it was from the 487th FS of the 352ndFG.

I've dealt with the same idea, Mac, and the only way I was able to deal with it was to make my new airbase close by to an existing one within DCS. Then make the short flight from the hard coded base to the newly built one, land, but not shut down the engine and then take off again. I found that if I shut off the engine, it would not always start back up again but maybe that was just a flaw in my landing or taxiing.