Re: Refresh Rate bug

@Jackrabbit710wrote:

do a search for need for speed rivals frame rate unlock. It had the same problem and uses the same engine

Fascinating. Doing just that and have found some interesting results. I also encourage others to search around. Two things I find immediately: a "fix" for it that some people figured out: https://www.game-debate.com/news/10227/need-for-speed-rivals-60fps-frame-rate-fix

But here's the REALLY bad part: https://answers.ea.com/t5/Need-for-Speed-Rivals/Command-line-augment-GameTime-MaxSimfps-33/td-p/2893488

Effectively, what that second link's discussion is about is that a multiple of 60 (or 30) is ok, because it doesn't break any car speeds... But a frame rate of 33 would end up with cars at that frame rate literally moving faster in game. So, if a car's (or, say, a starfighter's) speed is affected by the frame rate in-game, it makes sense why they lock it at 60, and why it will be so hard for them to fix (which, to be clear, they must do if they don't want the entire PC Squadrons world to explode). If the engine is built that way, then the fix is going to be really rough. Then again, if they fix it for this then at least it will be fixed for future titles that use the same engine, so maybe they can authorize more development resources to be thrown toward fixing it.

I have a bad feeling about this...

The more I think about this the more depressed I get. Effectively, what this would mean (if it applies here) is that they are going to need to overhaul the entire speed system. If a vehicle's speed is measured relative to frames rather than literal seconds, then everything regarding speed will be affected. This means it is going to be a long and hard fix, and a fix that almost definitely will introduce new bugs and vulnerabilities to cheating.

Add to that, I posted this message a couple minutes ago and it no longer was there; it has been flagged as spam. By whom, I wonder?...

Everyone: Start screenshotting your posts.

EDIT: One of my posts was restored (thanks EA); since it contained the same content, I deleted it above. Nevertheless, yes, keep a good record of your posts just in case someone flags it.

@SuperSmash88the launch arguments from NFS seem to do nada

edit

Did some more testing. It might actually have some form of positive effect, or I may be losing my mind. Not sure yet -- need to do more testing when I'm not on the clock at work anymore and can really focus 

---

@MastaFoo1010 wrote:

Did some more testing. It might actually have some form of positive effect, or I may be losing my mind. Not sure yet -- need to do more testing when I'm not on the clock at work anymore and can really focus 

---

Yeah keep us posted. Trick is, even if they help, I'm thinking they might "break" it in a way that it is (properly) cheating. Fingers crossed it's a real workaround that, well works.

The NFS bug seems fundamentally different to this bug imho.
Their entire game was capped, not just certain elements, or duplicate frames?

This issue is quite different with the high frame rate being actually rendered, but internal frames being duplicated.

I don't think the engine is the reason for it, it's the way the game is made.
Battlefield doesn't do this, Battlefront doesnt, Mass Effect doesn't do this. Same engine.

I think this is a bit of a false lead.

+1 with dutchDoctor : I remember the 30 fps caps from NFS Rivals 2013.

I was so happy when I discovered the trick on a forum to unlock framerate to 30 fps to 60 fps !

But on NFS rivals , it was a simple fps caps, 

Here , it seems it s more complicated ,  and honestly , I really afraid this bug will not be solved soon

Yeah, I hear you guys, for sure. My fear is that if the reason there is a cap (and sending dupe frames) is due to ship speed being measured against frames (as sounds like was the case in NFS, based on the result of the workaround they found for that one), then this really is a larger-scale fix. Like I say, it's come about far enough that they can't not fix it without it tanking the entire game on PC and PCVR. Just sucks that it appears it'll be a bigger deal to fix than we had hoped (and perhaps take longer).

Saddest part is that this game really could have been THE VR game for people to play when they buy a HMD and are interested in getting into VR gaming. As it currently stands, it's just one of the games to avoid for VR on PC. Really hoping they recover this.

Well, I know it's not Star Wars but here's hoping Project Wingman turns out great, that's my next 'look forward to' VR game

I think I have a real workaround after getting out of a chat with support, scratching my head, making dinner and then thinking of this workaround and giving it a shot.

If you have an RTX 2070 or RTX 2070 Super or any nvidia card than this workaround might work for you as well.

1. First, you need to create a game profile for Star Wars Squadrons in NVidia control panel. Here is instructions: https://help.ea.com/en-us/help/pc/pc-graphics-troubleshooting/#creategaming
2. Then, in your profile set the Max Frame Rate to the exact value of 60 FPS
3. Then in Star Wars Squadrons, open up settings and change the refresh rate to 120 hz (don't select that weird 59.95hz option)

4. Your CPU should no longer be at 90-100 degrees celsius after this change and should be running at a more normal temperature. Your graphics card should also be running at 60fps at a stable rate.


I think what people were saying before with the issue being the refresh rate has to be a multiple of 30 and this 59.95hz option in squadrons is mucking things up. I'm going to keep testing, but this seems to have remedied things for now. I have been monitoring my performance and temperatures with MSI Afterburner.

UPDATE: this solution worked well until I was playing in combat for a short period of time. To get even better CPU temps, I turned on Low Latency Mode and Vertical Sync was set to "Adaptive" in the NVidia Control panel. This allows me to play the game at ultra settings locked at 60 fps.

Getting CPU temps down is definitely a good thing, but I'm not sure that is related to the 60FPS lock... But that definitely is some good tips for CPU load; I just don't want EA to think that the players found some workaround for the 60fps-lock bug such that they don't have to work as hard on it. 😉

60FPS lock remains... and if it gives any additional impetus to you folks over at EA/Motive, someone with a Nvidia 30 series card should be getting WAY more than 60 fps; not needing to artificially limit their graphics card's power.

---

@WarGravy00 wrote:
@ManolocoxYeah but for a lot of us a workaround was needed to play the game, the cpu temperatures were dangerously high.

---

I understand, could be a different problem altogether or a problem linked to this one, but for you the consequences of running the game seem to be worse, with danger of damaging your hardware, it might be helpful for you to make another thread about your particular bug besides the post you made here, and follow both.

good luck in both cases and hope you don't damage your pc, i dont know if you made a mistake (typo) when you typed 3070, since those are not out yet or were making a joke, since that was not clear to me i just replied taking into consideration the thread objective.

any news on when this will be fixed?

not playing this game until it is

This will NOT be fixed...UNLESS they re-engineer it just for PC, at an early point in development someone decided they didn't want Little Johnny puking up after playing this on his PlayStation  VR, so they developed the game engine tick rate  to run at 30/60 to accommodate PS-VR perfectly, (I've tried it & even though horribly low-rez solid smooth frame rate & no motion sickness) unlike my Rift-S & RTX2080 (soon to be Reverb G2 & RTX3080 JUST for this title!!!!)  Is there any other x-platform VR between PS & PC?? if so what's it like on PC?  I AM GUTTED BY THIS.....JUST REFUNDING ISNT ENOUGH FOR ME....

Yeah it's a real bummer, I've seen countless threads on both run up to release and post release where people have talked about what they have bought specifically for this game, new GPUs and VR headsets being the most talked about. 

I own some decent hardware myself but it was not purchased specifically for this title, however, I imagined for months pre-launch that this could be one of the best VR titles to be played on PC. I too am gutted the game has launched like this. 

I believe EVE Valkyrie was/is X-play with PC/PS4. It runs very well on PC and looks pretty but I'm not a massive fan of the way the ships handle in game.

Aha get in, Epic wouldnt refund me but as I've been a long time user of the unreal engine and been active on their boards for years, moaned on there and strangely half hour later I got an email from Epic giving me a refund. 

Epic do have some integrity after all.

So now this piece of * is off my computer and the money returned I can leave this here and never return.

* YOU EA 

Yeah, if EA hasn't moved the bug out of investigation officially  (i.e. on the Known Issues post) by the beginning of this upcoming week, it'll be time to start having streamers and folks on YouTube warn others that if they are getting this game for PCVR, they should wait, or get it refunded ASAP before putting more hours on this game. I guess I shouldn't be surprised that even though EA decided to make a game without microtransactions, they still managed to mess up its launch with dishonest marketing and terrible communication about THE LARGEST (affecting the most people) bug in the game; find me a thread in this forum with even half as many comments in it.

If you are getting this for PCVR and haven't yet purchased Squadrons: don't.

CPU temps lol. This game isn't even hard on the CPU compared to many other titles, if you have temp issues in this game your CPU cooling is very much malfunctioning.

And FYI modern CPUs and GPUs auto throttle themselves a bit before 100c to prevent any damage, which reduces the performance of course but the refresh rate issue is absolutely NOT a performance issue, it's a rendering issue.

In regards to the cpu temps, I found that if I let the game boot up without a form of frame limiting like vsync, then the 1500+ fps it was running at on the main menu certainly thrashed the * out the cpu and max it out to 100% usage, which would then obviously cause an increased temperature.

That was the only thing on this shoddy arse game I did manage to fix. 

Dont know if that helps you or not 🙂

100 degrees is not good though shouldnt really be hitting those temps. Maybe take the heatsink or aio off your cpu, give it a clean and stick some new thermal paste on. Bit of a ballache though...

Or just uninstall this game 😉

@stevensred5  it s my opinion too unfortunately ☹️

 I m afraid it will not be fixed , the problem is in the engine of the game and they need to redevelop many parts I think.

this game has no future (no DLC , no Addons or new maps in multiplayer) and less and less people are playing it , I think dev will solve small bugs but they dont loose time to solve a huge problem like this (that s why I refunded very quickly (only 45 min of gameplay for me)

Let's just hope if they won't they at least admit it and just say so so that we can all stop wasting our time trying to get them to support VR on a game they built from the start "for VR."