WIP Beta released Barbent's Homerange (Alpha) 0.1a

Usually all maps work better on the second try, when the cached parts are just reloaded. But it is normal that it takes 3 minutes to load because of the Audio content that needs to be loaded (on my system, see signature).

 

Yeah... I tried to spawn a second car and it crashed BeamNG and broke my computer to the point where even google wasn't working because it was saying I didn't have enough memory... until I did a restart!

 

Maybe caused by a saturated memory or an HDD

 

Personally, even with a 1660 GTX (which is a pretty strong card) and a Intel Core i7 8700K wich can run very good in ultra mode on most maps, here i'm at around 10 fps...

Yes, when i run the map, apparently, more than 80% of the memory is used and it's the only thing that is "wrong" in the performance tab
--- Post updated ---

Well, my machine has 32GB of RAM. It doesn't run fine.

I have to resort to normal graphics for reasonable framerates.

 

I wonder about the performance issues, I can run the map perfectly fine on a GTX 1060, Intel Core i7 6700K and 32gb ram. In 1080p though. But I can´t run any map in 4k tbh.. So Homerange gives me better fps like Polish Roads for example...

 

That's weird. Because on my side, this map is really cahotic. Last time i tried runnnig it in normal graphics, and it started to run without any issues, until i opened the navigation map, zoomed in a little bit... and the game froze to death.

EDIT: This map does that again, and again, and again... Sometimes removing a vehicle is enough to freeze the game. Other times, going to the nav map freezes the game. In this current state of the map, it's unplayable for me.

 

Could definitely be something to do with not having enough memory

 

If 16 GB of memory is enough according to the creator, what is happening here?

 

My disorganisation probably has something to do with it.

 

Just turning the camera was enough to completely freeze the game...

 

I really wonder whats going on there... I get a stable 60fps on this map, on an older and inferior pc system than yours... maybe the problems on your end are related to something else?

 

The map needs RAM! Running it on a 16GB machine is not recommended. Also try to wait a bit, BeamNG is sometimes sorting things. The map was tested before release on 3 different machines with 16GB of RAM (even one with only 12GB) and was playable, it caused no crashes but had moderate FPS. 4GB VRAM is recommended.

 

I have 32 GB total RAM and 5,966 GB total VRAM. Do I have to upgrade to 64 GB of RAM?

 

No. That is enough. There might be a different problem.

 

Maybe my graphics card memory isn't enough?
I have for my GPU:
Physical Memory 2047 MB
Virtual Memory 2048 MB

 

That seems a bit less. Idk, what this virtual part of memory means but if only 2GB are able to be addressed directly, that might be not enough. Sorry, I am not a hardware expert.

 

I figured out that the VirtualRAM data i had didn't correspond to the actual VRAM you were talking about (visualram). I now found the good number: 5996 MB which is apparently enough.

 

I have only 4GB of VRAM (fiends laughing 'bout my poor graphics) and the map was created on this machine.

 

Oh. Do you have any clue then on what's happening?

 

Hint:
The long audio loading time does not mean audio is occupying much RAM. BeamNG is slow on initializing the audio emitters. Also the number of sound sources has not to be increased in the settings or anything. The audio files are very lightweight.
--- Post updated ---

No. Let's take a look into your log files if you like...