One of the best games I've bought!

[Robet.G]

Huge fan of science since I was a kid, picked up this game a few months ago and have been enjoying it for many hours.

The game engine is a shame though, especially on the physics performance side, severe lack of optimization.

Also memory management is just sad, this game takes more memory to run than GTA V, which is a 60GB game.

Other than that, the concept of this game is definitely one of the best.

Also the mods, loving the mods, especially FAR, adds so much more depth in designing planes.

[Starwhip]

Welcome aboard Robet.G!

I agree, the game is fun, but could use some memory fixes. Thankfully, with 1.1 coming Soon^tm, and the transition to Unity 5, memory management should improve significantly, because the physics engine can distribute the load over multiple cores.

Have fun out there!

[Speadge]

Welcome aboard Robet.G!

memory management should improve significantly, because the physics engine can distribute the load over multiple cores.

...and again:

physic-engine does use multiple THREADs, not cores. The Processor (Core) handling is an OperatingSystem-Task, not something the application can manage on ist own.

Above that, Multithreading of the physic-engine has absolutely NOTHING to do with Memory Management / fixes in Memory handling.

the one is the data that is stored and you can work with, the other is how fast you can work with that data on Tasks.

hope that helps in understanding, that 1.1 propably wont use (significantly) less RAM than 1.0 did.

Edited September 18, 2015 by Speadge

[Dman979]

Well, you can't have everything. Where would you put it?

But anyway, welcome!

[Starwhip]

...and again:

physic-engine does use multiple THREADs, not cores. The Processor (Core) handling is an OperatingSystem-Task, not something the application can manage on ist own.

Above that, Multithreading of the physic-engine has absolutely NOTHING to do with Memory Management / fixes in Memory handling.

the one is the data that is stored and you can work with, the other is how fast you can work with that data on Tasks.

hope that helps in understanding, that 1.1 propably wont use (significantly) less RAM than 1.0 did.

Yes, this is true. However, the new version of PhysX can distribute the load over multiple cores, not just threads.

IIRC, anyways. Gonna check the Devnotes.

EDIT: PhysX 3.0 can indeed distribute over multiple cores.

Edited September 18, 2015 by Starwhip

[Dunbaratu]

...and again:

physic-engine does use multiple THREADs, not cores. The Processor (Core) handling is an OperatingSystem-Task, not something the application can manage on ist own.

You don't hardcode how many cores to use, but using more than one thread lets the OS put some of them on other cores if it thinks that spreads the load better. When it's single-threaded you prevent the OS from being able to do that. When you write threaded code and don't hardcode how many cores to use, the OS can still choose to run the threads on on multiple cores if it wants to. There are cases where forcing it to pick certain CPUs is beneficial, but even if you don't do that, just making it multithreaded *allows* the OS to make it multi-core if it wants to.

If your program has N threads, then the OS won't use more than N cores to run it. It can't. Single-threaded therefore also means single-core.

Edited September 18, 2015 by Steven Mading

[Robet.G]

To be honest, the physics runs fast enough for me for the most part. It's the memory that's the bigger problem. I mean you want to install all those mods, but you can't because of the memory.

[Whizzkid]

To be honest, the physics runs fast enough for me for the most part. It's the memory that's the bigger problem. I mean you want to install all those mods, but you can't because of the memory.

1.1 should have a stable 64 bit version, so the 3.5GB memory limit should no longer be an issue.

[KSACheese]

Welcome, and we're all waiting for the 1.1 Unity 5 convert so you're not alone