Freezes are back..Not sure what else to say about this, at least game feels overall more smoother and my fps seem to fluctuate less. I did have to reinstall game because the game would crash every time it opened. Ever since then (late last night) I have been having freezes just as often as before opt in.
Some more evidence:
-
Played on DFW and some other non official servers and got the freezes.
-
But, on FNG01, no problems.
-
So, either FNG isn't running PB like it reports it is, or it has different PB settings then the other servers, or something is different about it. Why is it only that server where I am getting no freezes?
This is not a PB issue, at least that is not the sole cause. I recently upgrade to a AMD 290X GPU, and I'm getting these random freezes every now and again. It has nothing to do with what's happening in game as it sometimes happens right at the start of the round when nothing is happening, or when I'm spectating.
I did not have these issues with my old AMD 7770 card, and yes the old drivers are gone and the latest AMD drivers installed (even tried the latest AMD beta drivers). I'm posting here as I also had the issue during the latest opt-in, this is worrying as it makes the game very frustrating.
I have the freezes with 352.86 even with hud off trick. It happens after I play the game for more than ~1 hour. It's noticeable on round start when you start running, the screen can micro freeze for a milisecond every now and then. I'm using Gigabyte GTX 960 card.
I have my FPS capped at 120, this is how the graph and my fps look like at the end of maps like Coldfront and Downtown, still didn't find any explanation that made sense to me.
I have my FPS capped at 120, this is how the graph and my fps look like at the end of maps like Coldfront and Downtown, still didn't find any explanation that made sense to me.
I have my FPS capped at 120, this is how the graph and my fps look like at the end of maps like Coldfront and Downtown, still didn't find any explanation that made sense to me.
I solved this problem with going back to win7 from 8.1.
My graph looked EXACT the same, red game line spiking into the frame line.
Yeah, saw the post in the old forums. Tried running it in compatibility mode, didn't work though and I don't wanna go back to win7 for just one game. Guess I'm gonna wait for release and hope for a fix until then.
It's always been the driver and it's random and seems to work differently for everyone lol..
Current newest driver gives me second freeze but very seldom. Again December driver 347.09..or whatever it was..doesn't give me any, yet Wonkss said it did for him.
On a somewhat related note, when I went back to the regular beta last night I was too lazy to close out the game once I opened it to set fps to 122 and turn on smoothing. Performance was great and bullet reg was amazing. Tried a couple different servers, same thing. Played in a FN match, same thing. I think that for someone like me who doesn't have the CPU muscle to float the max, smoothing does more harm than good (almost like as it's trying to smooth the frames it's not presenting an accurate picture of the enemy or something). I'm going to continue to leave it off and see how it goes, but last night felt like it did for the first year of the opt-in before I got the new monitor and started messing with the ini. Anyways, just wanted to share that in case anyone else has a 120/144 monitor but struggles to maintain those framerates.
On a somewhat related note, when I went back to the regular beta last night I was too lazy to close out the game once I opened it to set fps to 122 and turn on smoothing. Performance was great and bullet reg was amazing. Tried a couple different servers, same thing. Played in a FN match, same thing. I think that for someone like me who doesn't have the CPU muscle to float the max, smoothing does more harm than good (almost like as it's trying to smooth the frames it's not presenting an accurate picture of the enemy or something). I'm going to continue to leave it off and see how it goes, but last night felt like it did for the first year of the opt-in before I got the new monitor and started messing with the ini. Anyways, just wanted to share that in case anyone else has a 120/144 monitor but struggles to maintain those framerates.
"bSmoothFrameRate=False" is smoother than "bSmoothFrameRate=TRUE".
At least the times i have done direct comparable benchmarks reading out frame times, "drawback" is that you're capped at 90 FPS.
They claim that these stutters are caused by parked cpu cores to save energy. I have not tried it yet but I am going to and report back. If you want to test it in the meantime, be aware that it makes changes to your registry.
According to this thread it has helped a few people:
On a somewhat related note, when I went back to the regular beta last night I was too lazy to close out the game once I opened it to set fps to 122 and turn on smoothing. Performance was great and bullet reg was amazing. Tried a couple different servers, same thing. Played in a FN match, same thing. I think that for someone like me who doesn't have the CPU muscle to float the max, smoothing does more harm than good (almost like as it's trying to smooth the frames it's not presenting an accurate picture of the enemy or something). I'm going to continue to leave it off and see how it goes, but last night felt like it did for the first year of the opt-in before I got the new monitor and started messing with the ini. Anyways, just wanted to share that in case anyone else has a 120/144 monitor but struggles to maintain those framerates.
"bSmoothFrameRate=False" is smoother than "bSmoothFrameRate=TRUE".
At least the times i have done direct comparable benchmarks reading out frame times, "drawback" is that you're capped at 90 FPS.
Question, is the network data sent from my client to the server based on frames or is it entirely separate from that? I know server tickrate is 30 hz, but how often does my client try to send data to the server? Is it controlled by the tickrate? Or is data sent every frame that my GPU produces, or what?
Comments
Twitch Channel|Steam
-
Played on DFW and some other non official servers and got the freezes.
-
But, on FNG01, no problems.
-
So, either FNG isn't running PB like it reports it is, or it has different PB settings then the other servers, or something is different about it. Why is it only that server where I am getting no freezes?
I did not have these issues with my old AMD 7770 card, and yes the old drivers are gone and the latest AMD drivers installed (even tried the latest AMD beta drivers). I'm posting here as I also had the issue during the latest opt-in, this is worrying as it makes the game very frustrating.
352.86 (may 19 2015)
Testing now for any issues...will report back shortly.
Have you tested on a non-PB server?
Knock on wood....Worked Flawlessly tonight....No freezes at all. (at least in my case)
i5 4690K/970GTX/16GB/XL2411/Win10
aastats.com
#Support Comp Mode
https://www.youtube.com/channel/UCN4YhM6jUB2MxVj8i3b9rhw
http://i.imgur.com/8FIf1aF.jpg
I love this community!
#Support Comp Mode
https://www.youtube.com/channel/UCN4YhM6jUB2MxVj8i3b9rhw
This is not an option if you play new games aswell.
My Youtube Chanel I AAPG Profile I AA2 Tracker August KILL COMPILATION
August KILL COMPILATION II
I solved this problem with going back to win7 from 8.1.
My graph looked EXACT the same, red game line spiking into the frame line.
Yeah, saw the post in the old forums. Tried running it in compatibility mode, didn't work though and I don't wanna go back to win7 for just one game. Guess I'm gonna wait for release and hope for a fix until then.
I love this community!
#Support Comp Mode
https://www.youtube.com/channel/UCN4YhM6jUB2MxVj8i3b9rhw
344.75 is my current driver on win7,runs flawless.
Current newest driver gives me second freeze but very seldom. Again December driver 347.09..or whatever it was..doesn't give me any, yet Wonkss said it did for him.
#Support Comp Mode
https://www.youtube.com/channel/UCN4YhM6jUB2MxVj8i3b9rhw
LETS GO PENS
At least the times i have done direct comparable benchmarks reading out frame times, "drawback" is that you're capped at 90 FPS.
http://www.tomshardware.co.uk/faq/id-1939190/increase-fps-cpu-intensive-games-windows.html
They claim that these stutters are caused by parked cpu cores to save energy. I have not tried it yet but I am going to and report back. If you want to test it in the meantime, be aware that it makes changes to your registry.
According to this thread it has helped a few people:
https://www.reddit.com/r/oculus/comments/2i8vqj/stutter_fix_for_elite_dangerous_dk2_hint_disable/
EDIT: This seems only relevant to computers with i5 or i7 processors
Question, is the network data sent from my client to the server based on frames or is it entirely separate from that? I know server tickrate is 30 hz, but how often does my client try to send data to the server? Is it controlled by the tickrate? Or is data sent every frame that my GPU produces, or what?
LETS GO PENS