Thought this was coming out in February, feels like it should have.
your memory must be leaking.
Thought this was coming out in February, feels like it should have.
PC version seems fine. 1080p/60 gameplay:
https://www.youtube.com/watch?v=qDQhelDg754
PC version seems fine. 1080p/60 gameplay:
https://www.youtube.com/watch?v=qDQhelDg754
If the framerate is CPU bound, won't the PS4 seem the same framerate issues? I thought the PS4 and Xbox One had very comparable CPUs.
If the framerate is CPU bound, won't the PS4 see the same framerate issues? I thought the PS4 and Xbox One had very comparable CPUs.
Looking really solid. Seems like PC is the way to go this time.PC version seems fine. 1080p/60 gameplay:
https://www.youtube.com/watch?v=qDQhelDg754
If the framerate is CPU bound, won't the PS4 see the same framerate issues? I thought the PS4 and Xbox One had very comparable CPUs.
That's not what a memory leak is. That was simply thanks to the save file growing to large for it to fit nicely into the systems memory.is that memory leak thing the same shit that happened in ps3 skyrim after a while?
if so can you expect that it gets worse the more hours you play?
not that loading times as long as 15min(thats a record,right?) aren't already worse enough.
wtf??
Älg;187265364 said:So, how does this guy actually know that there are memory leaks?
Älg;187265364 said:So, how does this guy actually know that there are memory leaks?
Älg;187265364 said:So, how does this guy actually know that there are memory leaks?
That's not what a memory leak is. That was simply thanks to the save file growing to large for it to fit nicely into the systems memory.
A memory is leak is a mistake in the garbage collector, objects are created in memory but are never deleted from memory when they're no longer neccesary.
Älg;187265364 said:So, how does this guy actually know that there are memory leaks?
And like NX said the problem is when you reload a save after a long game session. I don't think the problem is only the game save dimension.
I find his claims of a memory leak to be a bold statement. Haven't watched the video, but I'd love to know a method to reliable determine if something is a memory leak without consulting debug tools. For all we know it could be a thread stuck in an infinite loop eating up all the resources, or a deadlock for example.
That's not what a memory leak is. That was simply thanks to the save file growing to large for it to fit nicely into the systems memory.
A memory is leak is a mistake in the garbage collector, objects are created in memory but are never deleted from memory when they're no longer neccesary.
This seems like the opposite of what most games are doing, I.E. having all the demos on one of the console versions, then the PC version turns out to be naff.
The only games I can really think of where that's the case are Batman AK and Mortal Kombat.
Wow I didn't knew it. I was holding to buy Mad Max since I thought it was made by B team.OG JC2 team did Max Max.
JC3 team is another team...
Älg;187265364 said:So, how does this guy actually know that there are memory leaks?
A memory leak is a mistake in the garbage collector, objects are created in memory but are never deleted from memory when they're no longer neccesary.
He took this information from his usual source: his ass. Long loading times are in no sense evidence for memory leaks. He probably doesn't really know what a memory leak is. Because the problem with memory leaks is not that the program needs time to clear memory, it's that it's not clearing some unused memory at all.
Apologies for my wrong use of terminology. I didn't really want to jump into specifics. I should've used memory management instead of garbage collector.Leaks are not mistakes in a garbage collector. Garbage collectors are actually more reliable at reducing memory leaks. You can still cause memory leaks in garbage-collected languages by unnecessarily retaining references to objects that are not used by the application anymore. But unreferenced objects will be destroyed reliably. The most common cause of memory leaks are bugs in manual memory management. Aside, I highly doubt that garbage-collected languages are even widely used in the core of game engines.
PC version seems fine. 1080p/60 gameplay:
https://www.youtube.com/watch?v=qDQhelDg754
Oooh. Hopefully it's not too demanding on PC.
Yup. This is a PC game folks. Looks great.
Watch the video. Whenever shit goes down its slow mo time.Calm down children the average framerate is 27 fps. Are you spoiled?
Calm down children the average framerate is 27 fps. Are you spoiled?
Calm down children the average framerate is 27 fps. Are you spoiled?
Calm down children the average framerate is 27 fps. Are you spoiled?
Calm down children the average framerate is 27 fps. Are you spoiled?
Are you kidding?
CPU bound, eh?
I wonder how this is going to run on 'old' i5 2500ks and 3570ks.
Lol.... Drops to below 20 CONSTANTLY is fine?
Short dips when like a trillion physic intensive calculations are going on. This is unpatchable and unavoidable on these consoles.
Dude its not even comparable to fo4. I have played probably around the same amount of fo4 as that and havent come across anything as terrible as the fps drops in Just Cause 3. Its honestly a worse technical mess than anything ive seen on the system