Blooze

By restricting the available weapons for the airfields in the ME.

Run the update from the start menu

The best I could find was a road on the side of a hill at a higher elevation than the village. Maybe that will work. Screen attached with coords at bottom.

Sorry but still no joy. I think that there are bugs involved that are present even though the latest version of mist is installed as indicated HERE. I have tried to make a screen shot of the lengthy error message bit it won't take.

I'm sorry but I don't have a clue how to add mist or remove a previous version. I no longer have 1.2.16 loaded so I tried adding the latest mist lua file and ran it in 1.5 but no joy. Maybe Grimes will see this and find a quick solution. Please don't waste another minute on this. Thanks again

The option was in the graphics config file when 1.5 was first released like 1.2.16 but not working. After the first hotfix the option was no longer available.

I think it's important to re-assign the default Track IR hotkey commands to keys that are not also being used by DCS World view keys so as to eliminate conflicts. Try choosing new hotkeys within the Track IR software and then re-assigning the new hotkeys to your Saitek profile. Another suggestion is if you are using Teamspeak go to settings/options/hotkeys and make sure that keyboard and mouse only has been selected in the drop down menu in the lower right corner of that window.

That option never worked in 1.5 and was removed with the hotfix.

Yes, apparently when it crashed before it didn't have anything to do with your conversion. Thanks again.....by the way, I sure would love to get OP Saturn converted if you have time and it's not too much trouble. It doesn't look like slmod will be available any time soon. Thanks again.

If you run an update from the start menu and it just flashes, it means you already have the latest version of the 1.5 beta so you are good to go until the next update arrives.

Sometimes a picture really is worth 1000 words. :thumbup:

I had a pro clip but only after it broke did I realize that I had it on the wrong side which explained why it never did work as I had hoped. I now have gone back to the hat clip and have no problems. Although the guide (Attached) doesn't specify right or left side the illustrations seem to clearly indicate that it should be attached on the left side. This makes sense in that the pro clip has a slight curvature that if reversed could very easily cause issues that would also be made worse if the distance is too great IMO. tcp-quickstart-201105-folded.pdf

Considering some of the problems that I and others have had with pre-1.5 MP missions running on the 1.5 Open Beta MP server, I just thought I'd mention that I have been having much better luck by avoiding exposing them to the 1.5 ME. I do editing in the 1.2.16 ME and then just put them into my saved games DCS Open Beta missions folder and run them from there.

I have found that one of the most important factors in setting up Track IR is the distance between the camera and the hat clip or pro clip. Although this has been debated before, I am convinced that optimal distance is about 15 to 18 inches and any distance greater than that will increase erratic and overly sensitive performance. I might also mention that with the pro clip it's very important to have it on the left side of the headset. I use the hat clip and with very little tweaking have a sense of total and reliable control under all circumstances.

Absolutely incredible!

Yes, you create it using notepad and save it as autoexec.cfg then put it in your saved games dcs open beta config folder.

Has there been a consensus of opinion as to just what the best entries should be for the autoexec file for both server and client? I thought I had it right with net.download_speed = 1310720 net.upload_speed = 1310720 but now I'm not so sure considering the various numbers I have seen. Coff, should the entries for everyone be exactly like this? net.download_speed = 256*1024 net.upload_speed = 128*1024

I got it loaded and am looking forward to checking it out.

For me and others I fly with multiplayer for both server and client is very unstable with the current release. I feel confident that things will improve when some future patches become available so be patient folks and try not to jump to any conclusions too soon. Just sayin':music_whistling:

Although you may not know how to do this yet, I have found that the only way to improve the HUD view is to change the time of day of the mission in the mission editor so it occurs either earlier in the morning or later in the evening. The difference in ambient lighting will provide much more contrast and the HUD will show much clearer against the background.

Most of the missions I have hosted in 1.2 no longer function properly in 1.5 and I am sure there are many others that have experienced the same thing. If and when a patch is developed that offers compatibility with missions made in 1.2 we will probably see much more activity in the multiplayer servers.

It's just a guess but probably because Nvidia has not thought it necessary to update their definitions as things evolve with the many software titles that they support.

You will need a mic to use Teamspeak. Get it free HERE (64 bit client) and get it set up. Most open servers have their Teamspeak address shown in the server description window. Then just jump in and go. So many fear that they need to be at a certain skill level to join a multiplayer server but you will find that most servers are filled with a bunch of friendly folks just like yourself that are just having fun. You could register HERE and get on their Teamspeak server (scroll down to see who's on). There are usually a few guys flying a mission depending on your time zone. Either way, Just do it!

:music_whistling:

I have run many test missions and have come to the conclusion that flat only with flat terrain shadows on looks great with a minimal amount of flashing and maximum FPS.