Sign in to follow this  
Poppet

Prepar3D V3.4 Hotfix 2 Released v 3.4 ( 19475 )

Recommended Posts

Help AVSIM continue to serve you!
Please donate today!

OOOOH - Lets hope this contains the patch needed for FSL to release their A320 for P3D.

  • Upvote 3

Share this post


Link to post

Can't find where the issue of not dropping vas is adressed. My love weakens.

Share this post


Link to post

just iinstalled it and GOOD NEWS ist that latest ASN16 and ASCA ist working so no need to wait for update :-)

 

will try a flight and report back !

  • Upvote 2

Share this post


Link to post

An intriguing little footnote at the end of the Fixes and Improvements List; "Thanks again for your support and we wll see you all in 2017 with some major news". Hmmm....   Time to break out the popcorn?  :Tounge:

  • Upvote 4

Share this post


Link to post

An intriguing little footnote at the end of the Fixes and Improvements List; "Thanks again for your support and we wll see you all in 2017 with some major news". Hmmm....   Time to break out the popcorn?  :Tounge:

 

And the credit card(s).   :wink:

  • Upvote 2

Share this post


Link to post

Just in time. Please report if VAS improved otherwise see no reason to update

Share this post


Link to post

Just in time. Please report if VAS improved otherwise see no reason to update

Just doing a quick flight from ORBX EGFF to Aerosoft EDDF , my usual VAS check flight.

 

Currently over london and i have to say that it doesn't look that good... VAS still increasing and increasing.... will see what happens on approach

Share this post


Link to post

... And war "

  • Entities will now report DAMAGED_DESTROYED when health points reach zero or when they are in a crash state when connected in a DIS session."

Share this post


Link to post

Just doing a quick flight from ORBX EGFF to Aerosoft EDDF , my usual VAS check flight.

 

Currently over london and i have to say that it doesn't look that good... VAS still increasing and increasing.... will see what happens on approach

It's not about increasing (of course it WILL be increasing), rather about actual numbers. There is difference between 2.7 - 3.3 and 3.2-3.9 increases over duration of a flight. The former is okey, the latter will end with OOM in 99% of occasions

Share this post


Link to post

"Fixed a GDI memory leak with static elements when resizing panels" 

(inside joke ... anybody else get it?  Memory that just ... stays alive.  This earworm was a part of debugging processes for me.)

Share this post


Link to post

Can't find where the issue of not dropping vas is adressed. My love weakens.

 

Aggressively purging of scenery regions to prevent running out of memory at high slew speeds

  • Upvote 2

Share this post


Link to post

Just doing a quick flight from ORBX EGFF to Aerosoft EDDF , my usual VAS check flight.

 

Currently over london and i have to say that it doesn't look that good... VAS still increasing and increasing.... will see what happens on approach

 

Are you running out of memory at high slew speeds?

Share this post


Link to post

 

 


Are you running out of memory at high slew speeds?
 I'm sure they're referring to a worst case, slewing being the fastest way to reproduce the bug.

Share this post


Link to post

 I'm sure they're referring to a worst case, slewing being the fastest way to reproduce the bug.

Right, then normal speed should be no problem if already tested with fast slew??

 

Edit: but in my question to denali's post  ... I was just wondering if his first test was a normal or slew speed ....

Share this post


Link to post

Here is what I would recommend to do in order to evaluate whether VAS power was diminished after the HF.

1. Load a plane in the area of your interest at the specific time/date with clear whether, for example NGX SAS 737-600 at AS EDDF

2. Write the remaining VAS readings.

3. Apply the HF

4. Repeat Step 1 withe EXACTLY the same plane at EXACTLY the same time/date/weather (yes, even different paints could yield different VAS readings).

5. Check the readings and report back.

 

I'll do all these steps later this evening unless it will be required to update FSUIPS and coatle.exe 


Slightly offtopic, but I'd like to mention that when I was doing all these numerous VAS tests at FT EHAM I suddenly found out that FS2Crew for NGX eats 250-300Mb of VAS alone. Same with T7, but slightly less effect - around 150Mb.

Share this post


Link to post

Does this hotfix follow the usual recommendations, like uninstalling the client before running (and also maybe uninstalling content after backing up respective folders)..

 

and heres to the future in 2017 and no more worries on VAS in general :)

  • Upvote 1

Share this post


Link to post

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this