Out of virtual memory

[checkerz]

Anyone have a solution to help here? I am getting errors on restart and not sure what is causing them.

I can run graphics at 125 fps no issues, and have no problems running the game/tracks or anything once loaded in.

I dropped texture resultion all the way from 512 down to 128.

I've turned off "record demo"

Would running Shaders/Direct vs. Shaders Copy help this?

Tough to test as it only happens with full gates/servers it seems.

PC Specs:
Intel Core i5 4570 (3.20GHz)
8GB DDR3 1TB HDD
NVIDIA GeForce GTX 760

[Robert196]

Your graphics are just too high. It runs out when you use more texture resolution than your graphics card has.

[tyskorn]

How many gigs is your GTX 760? When you load into a race it will tell you how much texture memory you're using. If you're using more than what your graphics card has, as Robert said, you have run out of virtual memory.

[Pumaxcs]

760 comes in two versions 2GB and 4GB, keep 'er under 2048.

[jlv]

Try going down a step on model texture detail.

[Ddavis]

What are the numbers in your graphic settings?

[AWood]

Everyones already explained it. You used more texture memory than your cards vram.

I only have 2 gigs. so i run 128 with low model texture detail

[Shadow]

http://forum.mxsimulator.com/viewtopic. ... ct#p264616

Follow the 2nd step and apply the large address aware patch. I've done that to every mxsim snapshot for ages and it's completely eliminated the out of virtual memory errors. Just be aware that if you go over the vram amount you'll experience massive stuttering due to game loading and unloading textures onto the card vram.

[Wahlamt]

I had this problem on one of the localcross tracks (2014 series). I have a GTX660 2GB, I've sometimes accidentally loaded tracks using 2.4GB vram. Those times it has just lagged, even when I've tested 1024x1024 10/100 shaders direct, no mipmaps, no texture compressing, it has still loaded the track. Even though it took like 3 minutes. But when I ran out of virtual memory, it loaded for like 15 seconds and then the window saying that came up. It has never happened on any other track though.

[dylan22]

Could be a driver issue if your not maxing out your card. I had one Nvidia driver that used to give me the out of virtual memory. Then the next new driver fixed it again.

[Phathry25]

I THINK ITS BECAUSE YOURE OUT OF VIRTUAL MEMORY.

[Monsterenergy52]

I had this problem on one of the localcross tracks (2014 series). I have a GTX660 2GB, I've sometimes accidentally loaded tracks using 2.4GB vram. Those times it has just lagged, even when I've tested 1024x1024 10/100 shaders direct, no mipmaps, no texture compressing, it has still loaded the track. Even though it took like 3 minutes. But when I ran out of virtual memory, it loaded for like 15 seconds and then the window saying that came up. It has never happened on any other track though.

I wouldn't consider your card the problem on the Localcross tracks. We had problems on a couple of rounds with the virtual memory outage, and it was due to a certain model or statue. Even if you had everything on low you would still go out of vram with the track. Hope that makes sense considering I am doing this late lol.

[yzmxer608]

I THINK ITS BECAUSE YOURE OUT OF VIRTUAL MEMORY.

This guy knows what he's talking about.

[ShackAttack12]

I THINK ITS BECAUSE YOURE OUT OF VIRTUAL MEMORY.

Aka phathry is right

[checkerz]

Try going down a step on model texture detail.

I went down 2 steps, same with ground texture levels and down 10 on ground geometric, and down 25 on model geometric detail. I also dropped from 256 to 128 texture resolution. I can run the game just fine with 40 guys and higher settings once loaded, but it's choking somewhere in the loading process.

I was at 120 MB texture memory used and still was getting out of virtual memory.

With 39 bots and me on the gate (with a stock model replacement in) I'm using 99 MB of texture memory.

I guess I can try to run with all stock models and try that, but it makes no sense to me why I'm having to absolutely ruin the visuals of the game when it runs fine if it loads. Missing races because of it is getting a bit old, thank goodness I haven't built any of the tracks this year or I'd be pretty pissed to not get to race the stuff I put my time into... but next week is Lakewood, and that's about to change.