-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Assetto Corsa Competizione (805550) #1420
Comments
How is the performance for you? I'm getting ~30fps with everything in the lowest setting possible with an Nvidia GTX 770 and 396.54 drivers. Which makes the game unplayable (and comically ugly). I tried KDE Neon Bionic with the 4.15 kernel and Solus KDE with the same performance problem. I can confirm that the G27 works perfectly. |
The problem with the invisible cars are mine. I set accidentally the number of shown to 1. I think that this game can go to the Whitelist. @aboutafter I have more FPS in mid settings with a 1050Ti |
What could be wrong with my rig then? because when I say lowest setting possible I also mean 1024x768 resolution and resolution scale at 70. On Windows I got more than 144fps on low settings and 1080p and resolution scale at 100. |
Try this |
I played a quickrace with 5 opponents in Mid settings at 1920x1080 and got an average of 35-40 FPS. Is not perfect but it stays fairly stable to play (for me). I see videos in Youtube of people saying that the game hasn't a great framerate in Windows. I think that this could be optimized in future during the Early Access |
Pressing F8 gives me a lot more FPS (more than double). I can now play at 50-80FPS at 1080p. Only daytime though. At night the framerate is horrible. |
What does exactly F8 button? |
I occasionally do not have audio from the engine, but brake squeal/aero noise is still present |
If you press F2 you can see the hotkeys. I think it says there that F8 makes a screenshot. Why does that cap and uncap the framerate, I have no idea.
Yes, I have the same problem too. |
It runs well for me sometimes, but occasionally crashes while loading. Also getting the audio bug. But in general it seems the game is still pretty buggy by itself, so might be just that. |
It's an Early Access game, and it's possible this problems are problems that are present in windows also |
System Information
I confirm:
Issues
|
The game stills working great with Steam Play/Proton after the yesterday update (Release 2). You can see a video here: |
Mine stopped working. I only get a black screen at the beginning and I need to reboot the PC because it freezes. |
What version of proton you use? I use 3.7.7Beta |
3.7-8 Beta now. |
Does it work with version 3.7.7? |
This game suffers from the UE4 nvapi problem: #1374 |
After 0.3 update the game continues being playable. Important: Multiplayer online also works. |
In the last 0.3.5 hotfix ( https://www.assettocorsa.net/forum/index.php?threads/acc-release-0-3-discussion.52898/page-37#post-1011269 ): I'm not sure what this means, but we seem to be being taken a little bit into consideration. |
I have this errors yesterday, with 3.16-5Beta and 0.4 release of the game. I don't know if this problem is related to this versions.I see that in race loading screen, the record of the track is always the same (same time, same player), I hadn't noticed this before, but it's been going on since the game was released in Early Access. I don't know if is a Proton problem or Windows users have the same error. One more thing, after record the previous video I updated my GPU drivers and with 415.23 (with transform feedback) i feel a better performance of the game with my poor Nvidia GTX 1050Ti. |
Hello again. Finally today I could try the game on Windows. First, like I say in previous posts, there is a video before menu. In multiplayer, the ping is much more lower than in Linux. In Linux you can see pings more higher than 300ms and in Windows, these are normal (lower than 100ms). I think some time ago these were much lower. |
With the last release (6) the ping on multiplayer is much more low. In the race loading screen, i don't see the same record always. But the "Fatal error" mini-window message stills happening sometimes. As before, sometimes the music doesn't work, other times you hear everything except the sound of your own engine. |
Trying the last version of Proton (3.16-8 Beta) the game don't seems to fix the problems described in this post, but I have this crash window when I try to capture the screen with OBS: I don't know if the problem is related or has nothing to do with OBS |
DLSS works fine here with ACC with Proton 6.3 (non-Experimental). I'm using Nvidia driver 495.46 on Fedora 35. |
Well these are all the NVAPI logs I believe. It could be Nvidia drivers on OpenSUSE. The drivers are published at nvidia.com RPM repo hence I much whether wait for them to push all the changes from New Feature branch to Production branch before trying again. NvAPI_QueryInterface 0xad298d3f: Unknown function ID |
Interesting, the game is not even trying to initialize DLSS on your setup. Did you entered an actual race when collecting the logs? |
I tried a clean prefix but the DLSS Option is grey out so I can't select it. I tried modifying the menuSettings.json to enable it but the game does not react to it. This is a line I didn't post in my last post: So I believe when 1.8.0 first came out, the setting was available for me to enable but the game itself doesn't use DLSS. |
Sorry, no more ideas from my side under the assumption that you have no DLSS issues with other games. |
Hey jp7677, I figured it out. I needed to copy nvngx.dll and _nvngx.dll into the compatdata's pfx/drive_c/windows/system32 folder to get DLSS working. |
Compatibility Report
System Information
SymptomsNo force feedback in the game, even if the controller is recognized correctly. I can play the game, but there is a uniform resistance of the wheel, with no proper force feedback felt. ReproductionLaunch the game in proton experimental or 6.3-8, and feel no feedback. I am using a Thrustmaster T248. |
The problem you have is that this wheel don't have support, at least as far as I know. Perhaps you can try to ask for support on this Thrustmaster drivers for Linux: |
Hi, yes indeed. Just found that the https://github.com/Kimplul/hid-tmff2 project has a t248 branch that works for me. Im so happy! |
I found another problem: In this game, with proton 7.0-1 or newer, the clutch is recognized properly (previous versions dont), but the force feedback doesnt work! |
Updated the firmware of the wheel but the problem remains: ffb only works with proton version 6.3-8 (but clutch is not recognized). Versions 7 does not work. This looks similar to : #5582 |
Proton experimental did not work in the past, works now. |
I seem to be having that issue on ACC with a Logitech G29(with New-LG4FF drivers, on other sims I've tried with proton experimental it's fine(euro truck sim 2, rFactor 2, even the mentioned F1 2021), but this game has regression of FFB not working + further to that it detects completely different inputs to how the wheel works in proton 6.3-8. |
Severe performance issues in Multiplayer (Assetto Corsa Competizione) Issue transferred from #6972. Compatibility Report
System Information
I confirm:
The Proton Log looks Pretty Interesting if you ask me SymptomsI have extreme performance issues in multiplayer. In Singleplayer I have 138 fps in average, in multiplayer 35. In both single and multiplayer, the GPU usage is at 100% and CPU is between 64 to 77% in singleplayer and 33 to 47% in multiplayer Reproduction
|
Hello @tim-gromeyer, although it's not strongly hinted, it might be interesting to keep an eye on PCIe Bandwidth Utilization in NVIDIA's GUI utility application. My suspicion is that the game is exceeding the VRAM limit and part of the render hotpath is being bumped to system RAM by the NVIDIA driver. When that happens, there's a noticeable percentage spike in PCIe Bandwidth Utilization, and GPU usage remains high in that scenario. If that ends up being true, then you might lucky lowering some graphics settings. |
Hello @kisak-valve,
Do you mean NVIDIA X Server? If so, I can't see anything about PCI at all in the app
This is exactly what happens for me in GTAV at medium/high settings, but this is another problem.
Even the lowest settings barely give me about 60fps in multiplayer, in singleplayer everything is fine |
@tim-gromeyer - Take w/ a grain of salt, as we're on very different setups, but try adjusting the "number of visible opponents" setting in the video options for the game. While it's cool to stare at the whole grid, you often don't really need to see more than maybe 8? 10? I haven't drilled into actual traces to figure out why, but higher numbers here, and higher view distance settings increase max frame render times pretty significantly. I'm in VR, so we have differing requirements and setups, but I've found this to be the single biggest one-trick for resolving multiplayer performance issues. Beyond that, if you have any custom liveries hanging around, just get rid of them. The way they're handled by the engine can cause some really weird resource allocation lockups (on Windows as well). All said, kisak may be right, as you are right on the line of the "minimum" recommended configuration for VRAM availability (4GB), and half of the "recommended" (8GB). While some of those settings may help, that VRAM limitation could definitely be causing you some issues. If that's the case, texture level settings, AA (get rid of temporal), and resolution changes might help you "keep 'er going" the most. Hope you get it working! I have ~1800hrs on Linux with ACC, and would be glad to help if you get any more info. |
Non-critical nuisance issue that I haven't written up, but has been there forever, just for others to feel not-nuts: If you re-order your USB devices (i.e. switch around to different USB ports, remove things, add things, etc.), then the next time the game starts it may be confused about which device is which. In my case, this meant that it labeled my pedals as the previously-saved name of my wheel, and no inputs were going, and labeled my wheel as my keyboard, where the input axis were from the pedals. I don't know if this is an issue with an assumption the game makes about identifiers when saving settings, or whether it's an issue in Proton itself, but you can resolve just be re-binding your inputs, so it's not that big of a deal. System Information
Reproduction
|
I just bought the game and on my PC using PopOS, an RX 6600 XT, and Mesa 23.1.3 (the stock driver on PopOS), I am experience weird graphical glitches like a trailing/ghosting effect as shown in the link below https://drive.google.com/file/d/1l-D9jgDaKUa_8eOH4sgPCM9POpHfqnGw/view?usp=drivesdk Interestingly enough, this issue also occurs on my Steam Deck, which is running the same Mesa driver as my PopOS PC. Maybe this is a Mesa issue? |
I've been running into an issue where all control inputs seem to have the same ProductID which causes some overlap when binding controls. For example with my TH8A and my OpenFFBoard wheel connected via usb, if I bind the wheel steering axis, then restart the game, the control menu requires rebinding my steering which then shows up as "axis 1" on the shifter. I believe the problem is in the controls.json file shown below where I don't have a solution other than rebinding everything pretty much every time I play the game. Just posting here in case anyone has any ideas based on this information. I'm running Proton Experimental at the moment. Click to expand
|
Compatibility Report
System Information
I confirm:
Proton logSymptomsNo force Feedback while wheel axis works as expected, Force feedback works using fftest and on native linux games like ETS2 and ATS2 ReproductionUse Cammus C5 Wheel Base on this game |
I tried the same game on lutris using wine-ge-8.26 and force feedback worked when I override the wheel to make it use Dinput from wine joy.cpl game controller setting while ffb never works on any proton version even in other games like beamng where it works with the wine version mentioned before. @kisak-valve can you advice what could be missing in proton? |
PROTON_FORCE_NVAPI=1 is required for HDR to show up in-game. |
I can confirm that force feedback is not working with Proton Experimental - using Thrustmaster T-LCM pedals and a Fanatec CSL DD wheelbase. Inputs themselves are fine, and I can map all axes and buttons. Force feedback works good with native Linux versions of ETS2 and ATS, using hid-fanatecff experimental driver. |
Try with Proton 8.0.5 that's what I use and you need to make sure your device is part of SDL driver. if it is not than you have to use sdl hint
Replace VID and PID as per your model. More Documentation here |
Although it does look weird in the settings menu, as all my buttons are being mapped to my pedals (?) the FFB is working. But I'm getting some wicked stuttering on Proton 8. |
Compatibility Report
System Information
I confirm:
Symptoms
The game starts but initial video is not shown. Everything is ok, even Force Feedback support in my Logitech G27. The performance of the game is irregular
The text was updated successfully, but these errors were encountered: