There are options inside the simulator, don't worry.

Thank you Nuno for those wonderful news.

One thing less to worry about about. Now there's only only one left I guess...

Does v4 with increased LOD radius get rid of the monotonous landclass texture pattern visible from cruise in some parts of the globe?

2 hours ago, Hoang said:

I care, I still want to know how much memory the sim uses.
 

Physical memory usage (VRAM and system RAM) yes, but VAS is a meaningless measurement with v4. We have something like 16 exabytes of address space now, which is an unfathomable amount that nothing is going to exceed.

8 minutes ago, him225 said:

Does v4 with increased LOD radius get rid of the monotonous landclass texture pattern visible from cruise in some parts of the globe?

No, you will just see it spread out even further all around, to get rid of it you need better landclass than the default.

I was thinking of upgrading from 8 gig of memory to 16.  Add in a few add ons and a browser and it may not be enough.  It seems that 32 may be better way to go.  

41 minutes ago, Tabs said:

We have something like 16 exabytes of address space now, which is an unfathomable amount that nothing is going to exceed.

8MB is all the RAM anyone will ever need... ;-)

Unfortunately the RAM prices explodes these days. For example i bought 2 fast 8GB DDR-4 3200 modules for 85 Euro 10 month ago. Now they are at 140 Euro  .

6 hours ago, PhugoidEffect said:

v4 seemed more GPU intensive to me. I just hope my 1080 running 4k handles it good.

It generates more FPS as CPU providing more = more performance needed on GPU side.

This demo has absolutely zero value to me.

Show me how the sim performs with the NGX from FSDT's KLAX to FB KSFO in the FTX regions with high settings and LOD to the horizon.

Oh wait! You can't demo such a scenerio since the NGX is not available and the regions have not be optimized for v4.

I hope you can tell how pumped I am to try that flight.

4 hours ago, Hoang said:

I care, I still want to know how much memory the sim uses.

As much as it needs, until it approaches your physical RAM capacity, I would hope.

It's actually better to leave things in RAM that might be needed again rather than just dumping them to "save RAM" as soon as you don't need them anymore... you don't need to reload them when (if) you do need them again.  It's only when the program needs to load something and there's no room for it should the application start dumping things it is unlikely to need again.

If you have 16 GB of RAM and you've been flying for hours, I'd say P3D is managing memory poorly if it's not allocating 15 GB or so.  Empty RAM is wasted RAM.

From a performance standpoint, good memory management is always using all of it.

I don't care at all. If it climbs to 14GB or something like that, i'll just buy 32GB and forget about it

Is it not good programming practice to make your code as efficient as possible?

Horrible stutters on all the videos of v4 I watched on Youtube.

6 hours ago, TheFlightSimGuy said:

Probably that God awful orbx so cal.

If you think about it, assuming that ORBX stuff came from V3, I would say P3Dv4 now is getting sloppier in unloading objects.  10GB of RAM? That's insane.  64 bit does not mean you suddenly not care about memory.  The stutters also confirmed my suspicion that performance wise, the improvement is marginal.  I am waiting for tomorrow, when more people have a chance to see for themselves.

40 minutes ago, RoboRay said:

From a performance standpoint, good memory management is always using all of it.

You probably are not a software developer to say that.  64 bit or not, memory needs to be managed efficiently, leaving only items that are improving performance and that's all.  Using all of it is just bad coding.