ajax

Actually, I think that button gives you wind speed and direction, not temperature.

I found that in the air you have to use right-alt \, not just \ .

I'm glad that solved it. Regards,

I don't know if your problem is related to mine, but If the ctrl key is pressed while loading DCS, the activation window(s) will pop up. In my case, I had my TeamSpeak push-to-talk mapped to ctrl-ins (or something like that). If I happened to be talking on TS as the game was loading, I kept getting these windows popping up. Drove me nuts until I figured it out. I fixed it by simply changing to another TS key combo that didn't use ctrl.

I don't know what else to try as that's the extent of my skinning knowledge (admittedly, not much at all). There are some real wizards around, maybe one of them will chime in.

Did you put each skin set in its own folder?

{DCS World}\Bazar\Liveries\ka-50.

I use: Mouse-wheel click = normal zoom Top rotary = fine rudder control Thumb rotary (three bands: 0-33, 33-66, 66-100%) = zoom in/out Thumb slider (two bands: 0-50, 50-100%) = center TrackIR

The 104th recently implemented integrity checks. I believe export.lua is one of the files checked, so you can't use Tacview (nor presumably Helios) anymore on that server.

Good question Paraglider... seriously. I was flying the other evening on the blue side and chats were very difficult to read. If you find the file, please post back here. I, too, would like to make the change.

It works for me with the latest update. Did you overlook turning on exports in the net\config.lua file, perhaps? (I'm not 100% sure of the filename and can't check at the moment.)

Yes, someone else posted this bug several weeks ago. I don't remember who.

Right. Unless you're talking about the Ka-50, in which case you will see the dreaded orange-grid skin. It seems all the other aircraft will default to a stock skin.

FC3 is still new. I think what is happening is guys jump in, find out their mappings take a screenshot instead of the intended function, then leave to fix it. Who knows?

Just a few minutes ago on an =STP= server running Thunderstruck, as soon as a missile fired by a Ka-50 hit an enemy ship, the game crashed. I hope this bug didn't find its way back in. Has anyone else seen this?

Make sure your inertial nav system is up and running (speed showing on the HUD). The autohover will disable the autopilots if this is the case. Also, if you are below 4 m (or is it 10 m?), the autopilots will turn off.

There were some previous posts about "unbinding" a product from an account when World first came out. Here's one post: http://forums.eagle.ru/showpost.php?p=1514894&postcount=6 . Don't know if this is applicable at all.

If you copied and pasted the code into your post, then there is an error in stage 3: trigger.action.setUserFlag(tostring(random_flag_[color=Red]ta ble[/color][1]), true) Delete the extraneous space.

Then the dcs.log may shed more light on the problem than the me.log. Edit: By the way, your ME log looks almost identical to mine -- many of the same errors, and it hasn't seemed to affect the stability of the missions.

Does it crash while test-flying or while editing in the ME?

I have them installed so that I can play them if needed. This was especially important early on with DCSW 1.2.0 and its MP stability issues. Now, not so much. Once my squad moves to DCSW, there will no longer be a pressing need to keep them. The errors do not appear to hurt anything, and I can get rid of them by simply copying the referenced folders to the expected path.

Did a complete reinstallation, including deleting the DCSW and Saved Games folders and wiping the registry. Unfortunately, this did not fix the problem--the ME errors are still there. Do you think having BS1 and BS2 standalone installed could cause this? Maybe one of the DCSW .bin files was corrupted?

Thanks for checking. I will try reinstalling.

Yes, they are most definitely "stronger". A bridge that took only 6-10 HE S-8 rockets to destroy in BS1 now takes 6-8 S-13 rockets to destroy in BS2 World. (40 HE S-8 rockets wouldn't even do it.)

Interesting. When I first launch DCSW ME and create a new mission, the F10 options are greyed out (as mentioned). However, if I load an existing mission the F10 options become available. If I then create a new mission without exiting the ME, the F10 options are still available.