davethewave2

For my part from fsopen software. Open clouds works fine Open server does not as underlying network transport looks like it's now encrypted.

Verdict so far: My weather engine (Open clouds) worked fine with no changes which is what I expect as it works with all versions of P3D. So if your addon uses standard simconect then you should be fine. The networking side of multiplayer has changed considerably, not sure if it's encrypted now but these differences is why it's not possible to join up between the standard and steam versions of the game. You will need to open and forward UDP 6112 and 27016 if you want to host. Also, the old bug in multiplayer was players would join in a glider and spawn lots of towplanes by requesting a tow then releasing it. This bug seems to be there still. I left a session open for an hour to return and find it was running extremely slowly, suspect because of this exploit.

I doubt it's a different version of simconnect.

Thanks for the feedback guys, disappointed that they've removed the option to connect directly as it prevents both versions of fsx from flying together. However, if users are having to validate via a steam logon and can be banned from a hosting server then I can see a benefit in just using steam multiplayer. Something that was always a problem with gamespy/direct connect. IVAO/Vatsim I expect work fine as they really use the client in single player mode and inject other players with simconnect.

Can old versions of fsx connect to it directly at the same time do you know?

So it's been re-compiled with vs2013 so it might take advantage of new cpu features particularly avx (Sandy bridge onwards) and avx2 (Haswell onwards) Would be great to see if there is a fps difference between versions on someone who has a Haswell cpu. I somehow doubt it but you never know

Jim, I said I was hoping it would still let players connect directly, in the same way that with gamespy you could still by pass it and connect directly.

How do you know this Jim?

I'm just hoping their new multiplayer system will still let original versions connect directly

fsx was last compiled in 2007 with acceleration/sp2, therefore it can only target technology that was around at that time. Currently this means p3d takes advantage of directx11 and avx cpu instructions. Going forward I expect further improvements such as directx12 support (expected to increase performance to counter amd's mantel) and I'm sure there will be a 64 bit version at some point. At some point it will be a no brainer to upgrade but there will always be some that won't, just the same as some still fly with fs9! Since you get any updates for free until version 3 comes out, and it works alongside fsx, why not buy it now?

I'd never tried fraps with p3d with earlier versions so I'd just assumed that it was because p3d always runs in window mode as opposed to full screen.

Probably, it's not something I've tested as it's a free upgrade to 2.4, don't know why you haven't?

As you are probably aware, fsx is cpu bound, adding cloud shadows will not help the situation. If you have a fast video card try Prepare3D, it's taken the fsx enginge and moved more of the graphic work to the gpu and it supports cloud shadows (and cockpit shadows) right out of the box. I was surprised to take a stock fsx plane, stick it in P3D and cockpit shadows work.

Chrome works fine for me Bill. If its just this site then maybe the cookie is there but is invalid (Doesn't correspond to a valid token in the database against your user) Try deleting all cookies for avsim and let it create a new one.

Loving it so far. This is now so much better than fsx, don't think I'll ever go back now. Cloud shadows next

Anything is better than ie for so many reasons!

Would be useful if you tried with another browser so to confirm that this is an ie11 issue or a site/user problem

Hi Mike, It might be because your graphics settings are too high and your system can't cope with the extra load. If you turn your settings down does it still crash? If it still crashes please confirm what cpu you have. If you don't want to pursue this I am able to refund your purchase in full, if you want to do this please send me a private message with your email address registered with PayPal. Dave.

Had the same issue myself on a plain vanilla setup. Restart fixed it.

Some further research. 2288 weather stations out of 4922 are at the same height or below their nearest airport. This means you'll get problems at 46% of airports. What I notice though is that the weather stations are listed in a file and loaded at runtime. I've modified the file and dropped every weather station by 100 feet. This should fix 99% of airports. Download the file from http://www.fsopen.co.uk/software/openclouds/wxmapping.bin The file replaces the existing version in C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\weather MAKE A BACKUP OF YOUR ORIGINAL FILE FIRST Once Lockheed Martin fix the bug you will be able to revert back to the original. Note this is a temporary fix that will only work with open clouds as I've added an extra layer on top of the invalid layer. Dave

Can you confirm if you are using fsuipc? If so please try with it disabled.

Pete, I've just flown from there with no problems, I'm in the Robinson 22 as shift+6 gives you a panel with a nice temp gauge on, and I'm low to the ground. The weather station is at 790 feet, and the airport 791 feet so I'd expected this to work fine. Once the weather is set, choose world, weather, select userdefined then click customize. Now select A specific weather station (Clealand-Hopkins is shown) and push advanced weather. On the Temp/Pressure tab you will see a drop down box, with the layers in feet. The first layer should be 790 and be very hot. The second layer should be 793 and set correctly, around freezing today(Brrrr) Anyway, when I hold shift+z in the Robinson it shows my altitude as 794.5 feet. I'm therefore above the first bad layer and sat 1.5 foot in the good layer. Pete, please can you check the above and report back.

1. CTD Issues. When you first start loading all the weather is injected in one go, this would cause fsx to be unresponsive for a bit depending on machince cpu. I experience similar on P3D but suspect this will be casuing the CTDs above. Hope to slow down the initial injection in 1.17 today. Should fix CTD problem. 2. High Temperatures. Most weather is injected at the weather stations that you can see on the map in the sim. Each station has an elevation, The larger airports all have a weather station close by, at a simliar but not necessarily the same height as the weather station. As stated above, there is a fault where any time you send weather, even without setting the temp, a temperature layer is added at the height of the weather station at 75C and another one about 10C at great height. As you slew upwards your temp slowly drops from one to the other. The fix I put in 1.16 yesterday adds another temp layer immediately above the weather station (one metre above), and others higher so the temp drops to well below freezing at height. Where I tested this yesterday this seems to work fine. I suspect the issue now is that where the weather station's height is below the airport you won't experience the bad layer, where the airport is lower then you will, perhaps only for the last few feet but probably all the time you are on the ground. The other problem is that most small airports, and some larger airports don't have a weather station at all, I looked at one yesterday(U82) and the airport was 1500 feet below the nearest weather station, therefore the temp was 75C for the first 1500 feet then suddenly dropped to -2C. I'm going to do a bit more investigating today but for the moment I'd expect 50% of airports to be correct. Will report back later.

Affinity masks means only use the cores you select. If you have 4 cores selecting all four will make sod all difference. Since win 7 I have seen no proof of any benefit using affinity masks.

Hoser, sent you a PM.