Attention:
The current patch (only DX12 Raytracing) causes the game to crash in the career menu. In my opinion, this is due to a lack of optimization by Frontier. There are no issues during race weekends (replays). I'm already working on a hotfix, but it probably won't be available until after my vacation. I apologize for the inconvenience.
Patch Notes:
After a long effort, I managed to get Raytracing and Lumen running in DX12. You can find it in the setup under the folder "RayTracing Variant Fullscreen - DX12". Currently, I’m only providing the fullscreen variant (other versions will follow eventually). This version might not work with AMD graphics cards, but unfortunately, I can't test that myself.
The DX12 Raytracing version demands significant hardware resources, so be aware of this if you plan to use it. If you encounter issues when starting the game, you can try adding the following to your Steam launch options: -USEALLAVAILABLECORES -dx12 -raytracing (though this shouldn't be necessary).
Updates:
All updates currently apply only to the DX12 Raytracing Fullscreen version. All other versions remain at version 3.1. Aligning them with this update would require a considerable amount of work. Since I’m heading on vacation, I wanted to at least make the new version available.
- DX12 Raytracing and Lumen
- Fine-tuning of lighting
- Improved reflections in car mirrors, making them clearer and more distinct
- Reduced ghosting in rain, but slightly more on dry tracks (unfortunately, both can't be optimized simultaneously; it's like a slider I can shift from one side to the other
)
- I've decided to make my setup file code available for those who want to review it to ensure there's no hidden virus or even help identify issues some users are experiencing.
- The mist in the rain should now appear thicker and more intense.
- Slight FPS improvement in rain.
As always, please report bugs, glitches, and issues in the discussions so I can look into them.
Known Issues:
I tried to capture the raytracing shadows and reflections in the screenshots below, but it's naturally hard to showcase in static images. I didn't want to draw red circles around the reflections. I think those who know where to look will notice them.
- On some tracks and in certain areas, the road surface appears muddy in regions not focused on by the camera.
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
Patch Notes:
As mentioned several times before, I believe that ray tracing in the game provides no visible advantage. In my opinion, it simply doesn’t work with DX11. Thus, it seems to be merely marketing for the mod
- Even less ghosting than before. (I believe I've reached the maximum possible reduction here.)
- Raytracing and Non-Raytracing versions are now on the same technical level.
- Increased FPS through various adjustments and optimizations.
- Reduced washed-out ground textures outside the camera focus (there will still be some depending on camera settings, just to save resources).
- Shadows now less frequently exhibit fine crosshatching patterns.
- DX12 available as an installation option for Fullscreen and Borderless Fullscreen.
- High-resolution environmental shadows (e.g., shadows cast by halos on vehicles).
- The setup.exe no longer requires selecting the main folder. (Simply choose the resolution and variant you want to use, such as Raytracing, DX12, etc., and then install.)
- The setup.exe now fully supports all 4 offered languages: German, English, Spanish, and French.
If you really want the best visual experience (like I do), then use the DX12 version because Lumen works much better there, and you can see significantly more and better reflections. If someone experiences very low FPS in the menus where you manage everything, I still recommend the DX11 version. These are all the variants that do not have DX12 in the description.
Some players receive a virus message. HEUR:Trojan.Win32.Convagent.gen
As far as I can tell from my side, it is not a virus. I have written the code completely by myself (I assume this is also the reason for the virus message as the code is so bad that it is suspicious)
Of course I can understand that you are afraid.
Of course the old method is still possible as shown in the video below.
Simply copy both files to C:\Users\**USERNAME**\AppData\Local\F1Manager24\Saved\Config\Windows
How to install the mod:
How to uninstall the mod:
- Extract the ZIP file to your desired location.
- Run MaximalGraphicMod Setup 3.1.exe.
- Choose the language.
- Select the resolution and variant.
- Click Install.
Uninstall it like any other Windows program:
Why can't I make a selection in the setup after choosing something incorrectly?
- Go to Start > Settings > Apps > Installed Apps
- Or, navigate to where you installed the files, usually here:C:\Users\**USERNAME**\AppData\Local\F1Manager24\Saved\Config\Windowsand use unins000.
This is normal. If you made a mistake during installation, such as choosing the wrong version, resolution, or a different folder than specified, you will need to uninstall the mod first. After uninstalling, you can reinstall it and make the correct selections as usual.
Alright, here we go again.You can tell I'm not a programmer.But first, it should now also work via the Setup.exe (MaximalGraphicMod Setup 2.9).
The only thing you need to do now, aside from selecting the resolution and the type of mod, is to specify where the unpacked folder is located. I plan to fix this in the future, but I need more time for that. Probably not before Monday or Tuesday.
I would appreciate it if you could give me feedback on whether everything works this way.
![]()
![]()
A folder had a really weird name. For now, it should be fine. Sorry, it's too hot.
Jesus there is still a typo
So as long as I work on a fix.
I uploded the files the old way.
So you need to choose youre resolution and copy&paste the both files.
The oldschool way.
Here we are again, one day later, with a bit clearer perspective. I even discussed this with my wife.
Just shows how old I am.
My wife also said, “Oh, it doesn’t matter what others say (I chose the family-friendly version). Just go ahead and do it.”
I want to apologize to everyone for making such a big deal out of it. Maybe I overreacted, I don’t know, but I was just really frustrated yesterday. At that moment, it was all just too much for me.
And it seems the interest here is much greater than I initially thought, which truly honors me. (See my TL;DR post in discussions for more details.)
Of course, I haven’t been idle; I’ve put a lot of heart into this, with about 5 hours of daily work just on the mod. (I know, I’m crazy.)
So, I present to you Version 2.9:
Quick Guide and Introduction:
- Improved performance during rain (Note: The quality on dry tracks might suffer slightly as a result)
- Blurry or jagged curves should be less noticeable now (I’m still working on this and haven’t pinpointed the exact issue yet.)
- Ghosting should occur even less frequently.
- Shadows under cars should now switch to a lower resolution later.
- The mod now includes its own setup, which should make it easier for any player to use it.
Open the executable, choose the language (currently German, English, Spanish, and French are available), in the next window, you’ll see the folder where it will be copied to (the correct folder should be pre-selected in theory; if not, you can adjust the target folder). Below that, you can select the resolution you use in the game. In the final step, you can choose whether you want the Raytracing version in fullscreen or borderless fullscreen, or either of the two options without Raytracing.After clicking continue, you should normally receive a message saying that this folder already exists; you can and should confirm this. Then click Install. If you no longer need the mod or have installed the wrong version, you can now easily uninstall the mod through Windows like any other program. Alternatively, there is also an Uninstall.exe in the target folder that removes everything.
One more thing: if you receive a virus warning, I can assure you as far as I know that there is no virus present. Only the two .ini files are copied to the folder, and the code for the Setup.exe was entirely written by me. I mention this because after the 20th compile, I received a virus warning for no apparent reason, despite no changes.
I’m not really a programmer, so forgive me if it’s somewhat primitively coded. I’ve done my best and can’t see any compile errors anymore.
If you have any questions, suggestions, or bugs, you know where to reach out.
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
I have made the difficult decision to stop providing updates and to take down what is currently available. I simply don't have the nerves or time to deal with being overwhelmed by PMs and comments in discussions every day. I’m truly sorry. The user duestereLegende insists on getting credit for something he believes I copied from him. Here it is: all of it is from you. In the future, you can download his work instead. I’m sure it will be very similar to mine soon. I’ve been doing this year after year for the Formula 1 Manager and have never experienced anything like this before.
Foreword:
If you truly want the best graphical experience, you should definitely use the Raytracing variant, as it exhibits almost no ghosting (at least in dry conditions). The NON-RAYTRACING VARIANT still shows visible ghosting depending on camera settings. I just want to make sure no one complains later, saying there was supposed to be no ghosting here.
As requested by some, here is a version that should provide up to 20% more FPS in the rain. Unfortunately, more FPS usually comes with drawbacks, namely quality. As can be seen, it's not possible to have both in rainy conditions. To avoid compromising on quality, I opted for a different approach. This method reduces the number of high-resolution pixels in the image. This can sometimes result in high-resolution textures loading more slowly. For example, in certain situations (primarily the screen in the pit lane where you select setups, tires, etc.), textures may appear blurry for 1-2 seconds before they load in high resolution. Additionally, in race shadows, you may notice a slight crosshatch pattern. But, as they say, you have to take some hit somewhere.
Furthermore, the NON-RAYTRACING VARIANT is now on the same technical level as the raytracing version.
Personally, I still prefer version 2.4, which offers the best graphical experience without any visual compromises.
Another tip: If you have monitors with high refresh rates (90Hz, 120Hz, etc.), I recommend using them. A higher monitor refresh rate can further reduce ghosting, but this applies only to the Raytracing variant.
Patch Notes:
- The racing line should now generally be less shiny and no longer reflect cars on dry surfaces. However, it will still stand out from the rest of the track as it represents the cleanest part of the surface.
- Added resolution 1477 x 831.
- Fine-tuning for soft particles.
- Driving in the rain should provide slightly better FPS. (Work in Progress)
Patchesnotes:
- Just added missing Screenmode commands for 2 Resolutions.
Patch Notes:
This patch is currently only available for the RayTracing version. Please note that this version can be used by everyone as it does not require GPU RayTracing cores.
- Added Stronger Wind: Unfortunately, this effect only impacts the flags on the track.
- Improved Clouds: Clouds are now more visible and dynamic.
- Enhanced Particle Effects: Improved effects for accidents, braking, gravel, and grass.
- Particles Now GPU-Calculated: Particles are now processed by the GPU for even better visuals.
- Added Particle Collision: Particle collision has been added. Due to the small size of the particles and the rapid occurrence of accidents, this is difficult to see.
- Better Accident Representation: Accidents are now depicted with more detail.
- Minor RayTracing Adjustments: Differences should be minimal and not easily noticeable.
- Less Eerie Driver Eyes: Driver eyes now appear less unsettling.
- Removed Duplicate Lines: As always, a few duplicate lines have been removed.
- Better Sound: Engine sounds should be crisper and more defined.
- Additional Sound Options: General enhancement of sound settings.
- Tire Smoke When Braking Hard: Smoke will now be visible from tires when braking too hard.
- Kicking Up Gravel: Driving into gravel will now cause stones to be kicked up.
- Kicking Up Grass: Driving through grass will now cause grass to be kicked up.
An update for the non-RayTracing version will follow. Unfortunately, I cannot provide a specific timeline at the moment due to limited availability (Sorry).
There are currently quite a few commands that serve no purpose. So, don't be surprised. However, they do not negatively impact performance.
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
Drum roll...
I am happy to announce that I have conquered the beast known as Ghosting. At least by 95%.
With Version 2.0, I present to you a version where ghosting is reduced by 95% on dry tracks and about 80-85% in the rain.Technically, it would be possible to eliminate it completely.Unfortunately, I don't have a NASA computer, and most of you probably don't either.Nevertheless, I claim to have made a huge leap forward with this version.
Of course, there are still some scenarios where slight, brief ghosting may occur, such as with a fast camera and changing lighting conditions. Or in the rain, where many factors come together, such as a wet track, water being splashed by cars, and rain from above. This makes the calculations very difficult.
But I would say that now you can comfortably use TV Camera 1 without constantly seeing ghosting.
Currently, this works very well only with the Ray Tracing version. Although it should also be much better in the non-Ray Tracing version, there is still significantly more ghosting than with Ray Tracing.
However, everyone can safely try the Ray Tracing version as it does not require dedicated cores of the graphics card.
I look forward to your feedback.
If you like my Mod, leave me a 5 Star Rating.
o here we are. Initially, I didn’t plan on offering a Ray Tracing version. Firstly, because no one had ever asked for it; secondly, I’m unsure how many players can actually utilize it; and thirdly, in my opinion, the benefits such as improved reflections and shadow rendering aren’t significant enough. Especially since my version is already quite resource-intensive. However, due to the numerous private messages I received asking if I could make a Ray Tracing version, here we are. I actually had a Ray Tracing version ready but had set it aside. But if the players want it, I’m happy to offer it.
I still offer both Version for all Resolutions 1 with RayTracing 1 without.
Patchnotes:
- Raytracing added for Shadows and Reflections
( Raytracing on Cars, Helmets,Perimeter advertising, Asphalt, on Wet Track)
- Tessellation added.
I tried to capture RayTracing as good as possible but some Reflections are not visible when I Pause the Game.
And perhaps one more thing I want to mention here before anyone says that this is not possible because of whatever reason.The offered ray tracing is controlled via the standard graphics card cores, which means that theoretically any type of graphics card can render it.Why is this the case?This is because, although Nvidia graphics cards have dedicated ray tracing cores, the actual ray tracing only works with DX12.And DX12 along with ray tracing cannot be cooked here.
![]()
![]()
![]()
![]()
![]()
![]()
On this Patch I tried to max out the possible Details on and in the Car, like the Steering Wheel. I removed the half Res Front Wing Resolutions.
Also Shadows should scale on a better Distance.
Patchnotes:
- More Details
- Higher Car Resolution
- Better Shadow Distance
- More realistic and clear Asphalt
- Surround Sound for every Resolution
As usual I recommend to not use Camera 1 because on this Camera still Ghosting is visible (more or less)
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
As wished by 2 users I have added 2 Resolutions:
7680 x 4320
1280 x 800
So I think i find the problem with the lags in the Menu.
Its the DX12 API.
So I force the Game to use DX11 API.
Actual im not sure will this drops come from DX12 API and only in the Menu.
Dont want to blame frontier but yeah u guys know
Also as usual some minor balancing and fixes.
This Patch is just a Hotfix for missing Buttons on Wheels.
And I added Resolution 1366x768 as wished by a user.
You might be wondering why this guy posts two updates back-to-back. What’s the difference between Version 1.15 and 1.15a?
Primarily, Version 1.15a offers the best possible visual quality. Additionally, the previously grainy shadows have been replaced with super high-resolution shadows.
But why two updates?
Because Version 1.15a comes with the drawback that ghosting (trails behind vehicles) is more pronounced. To minimize this, I personally recommend not using the 1st camera setting (TV Camera). In the 2nd camera setting, ghosting is almost non-existent. Of course, in all other camera settings, it’s not an issue either.
Overall, I would say that this is the better version. However, since everyone has their own opinion, I am offering both versions for download.
As always, I strongly advise against using any upscaling methods, as they can make the image look considerably worse.
Here is a comparison of the shadows between Version 1.15 and 1.15a.
VERSION 1.15
![]()
VERSION 1.15a
![]()
If you want the version without ghosting, you need to click on "History" at the top. This will bring up a list of all released versions. From there, click "Download" on the far right of Version 1.15.
![]()
Patchnotes:
- Minor adjustments.
- Best sound for every resolution.
- DX12 for every resolution.
Patch Notes
- No more grainy overall image.
- Minor updates to reflections and lighting.
- Car shadows in the rain. (Previously, cars appeared to be floating or sliding on rails.)
- Increased rain details on the track.
![]()
![]()
![]()
![]()
![]()
![]()