0.22 Discussion thread | Use Safe Mode before reporting

Strange issues with the World Editor: after changing rotation a few times I cannot drive my cars anymore, and after screwing around with the editor for a while the editor windows (i.e the one for position and rotation) disappear.

Next time i'm ingame i'll take a screenshot to show what I mean.

Speaking of World Editor, the World Editor 2.0 thread keeps crashing my Waterfox for some reason.

 

You can regain control of your vehicle by pressing ctrl+L after exiting the editor, you will have to do this every time you need to drive, however.

 

floating letters?

 

Any plans on adding a function to the Post Crash Brake that turns off the engine, like this very old mod?

 

Hey Devs! Hope all is well, but unfortunately I do have to report an issue as I've surprisingly hadn't had many (considering I'm using a Intel HD 620 for the time being until I can get my hands on an adequate system). Specs: Core i5 7200u, SK Hynix 2x4 8GB DDR4 ram, and a little Intel HD 620.

So the issue started today, and I really have no idea how this came about. Part of me thinks its a driver issue, or power management, but i checked the power management, and my Intel gpu settings are already on Max Performance via the command center. That I know, second being driver related, but I don't think it is, since it does it only when I spawn into a map after the first initial one.

The Issue: I've been playing with all the settings turned down to low, with the exception of texture detail, and FXAA. I've also capped the game at a steady 30fps and it's been fine.....until I switch maps. Once I do that, the game just outright performs at this (I'm going by the in-game performance monitor): [FPS: 1.00 max: 1.08 min: 1.00 mspf: 1000 waitforGPU: 1001.94]
I started the game, went to Gridmap ran awesome. Then I switched to Utah (Which before this issue I averaged 34.7 FPS, with a low of 29.6), and then this is what happened

(I went into free cam, and just pointed at the sky to see if it would even move, but it didn't)



Honestly don't know if my fellow Intel GPU people is experiencing what I am, but ouch does it hurt to see this.

 

I would just exit the game (or at least exit to menu) every time you switch maps for now. I'm not sure what causes this, but I have definitely seen worse performance after switching maps - you're not alone

 

Well glad I'm not the only one! I've tried that but it still acted the same (although exiting the game is pretty much the only way right now that it'll run great, so 100% agree with that), but I just now noticed as I launched it from Steam, my brightness settings changed. So I went to display settings, to the graphic's settings, and it was on the setting let "Windows Decide" so I changed it to High Performance, and....now the game won't launch right. (Now it's 100% at 1.00 FPS even in the menu.)

*proceeds to yeet laptop* lol

My guess is most likely a driver issue idk might as well see what happens. Until then, classic Need for Speed games here i come.

 

wen dextop?

But yeah, it's an issue to be looked into - certainly work-around-able, but it exists nonetheless

 

When i put the Fps limiter on 60 fps the game gets laggy, keeps jumping from 54-58fps
Today i finaly found out that when i put it a bit higher like 66 fps the game runs stable on 60 fps
So im happy now Not sure if its a bug or on my side but maybe it helps other players to get 60 fps

 

Something me and my brother found last night trying to get his game to work. When his wheel was plugged in, the game would launch in the background but not open, however when his wheel was unplugged, it would open and run just fine. We found a thread applying to an older version of both the game and Logitech's G-Hub, and the fix worked. Just figured it throw it out there that the current version of beam and Logitech's G-Hub are causing this problem again.

 

Well aware of that but Update: The game is officially unplayable. I can confirm that in safe mode it's the exact same (And I can confirm mods did not cause the issue). I had just launched the game right now, popped into Gridmap, clutched kicked my 200BX, and it went from a stable 30.9 FPS to 5.92 then 4.67, then right back....to the dreadful 1.00 FPS. What shocked me was it all happened in seconds....like how. It's depressing, but hey I do have other games. Just sucks this one just decided that 1.00 FPS was perfect. Welp maybe they'll address this soon. That's all I'll say on this matter, pretty sure they've gotten many reports of this so I'll let it go.

*Note should've said this first:

I had CPUID Hardware monitor running, and I can confirm I wasn't thermal throttling, as it was one thing I thought it would've been, but my little dual core i5 never touched 90'C or above (had a max of 76.0)

I'll see if maybe when the next Intel driver drops, this issue goes who knows?

Until then, it is what it is.

 

Have you tried running it at the lowest graphics settings ? I've never had this issue and i have 2 gb less and a worse cpu.

 

The TurboFan hubcaps on the 18x8 rear hirochi lightning wheels look like this

 

those screws want to destroy anything they touch lmao

 

aren't they supposed to be transparent?

 

Ooooh totally forgot that.. transparent hubcap hubcaps.

 

It sounds the bolts stick out about 2.5 cm!