guenseli Posted September 22, 2014 Report Share Posted September 22, 2014 I'm (and others) testing out a patch that is currently listed as v2.4 ... has a list of fixed issues in the .chm. It's an RC so I assume it's going to be released relatively soon source P3D patch is imminent, Pete is starting into vacation? ;) Link to comment Share on other sites More sharing options...
Pete Dowson Posted September 22, 2014 Report Share Posted September 22, 2014 source P3D patch is imminent, Pete is starting into vacation? ;) Er, yes. I'm off from first light this Thursday, 25th Sept, back on Wednesday 8th October! Germany-Austria-Czech-Slovakia and back. I reckon L-M are timing these things deliberately! That's every single release since 2.0! There's no point me working with the Beta releases. I did that before but by the time I've sorted it another is out and I start again, so I decided to await the release. Sorry. Regards Pete Link to comment Share on other sites More sharing options...
Waterman981 Posted September 27, 2014 Report Share Posted September 27, 2014 I reckon L-M are timing these things deliberately! That's every single release since 2.0! You may be right there... Perhaps we should get your schedule a year in advance... Just to plan accordingly. ;) Link to comment Share on other sites More sharing options...
GHD Posted September 27, 2014 Report Share Posted September 27, 2014 The update is due on Monday. Link to comment Share on other sites More sharing options...
vgbaron Posted September 27, 2014 Report Share Posted September 27, 2014 Rob Ainscough has stated that the FSUIPC version he is using is working as expected with 2.4. Vic Link to comment Share on other sites More sharing options...
Andydigital Posted September 28, 2014 Report Share Posted September 28, 2014 No it doesn't, it will partly work like it always does, but every feature will not be available, things like wind smoothing, mouse macros and friction changes will not work as the memory addresses change with every update regardless of how small the changes Lockheed make, even a one bit change could potentially break FSUIPC compatibility if it causes the memory addresses to shift. Link to comment Share on other sites More sharing options...
GHD Posted October 4, 2014 Report Share Posted October 4, 2014 In my case (with Tessellation off), it causes an R6025 error. With Tesselation on it doesn't. Removing FSUIPC V4.936 cures the problem with Tessellation off. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now