0 of 0
File information
Created by
SammiLucia robber804 and LazorrUploaded by
sammiluciaVirus scan
Safe to use
Notifications
7075 comments
Join The Ultra Place Discord For the fastest support and releases. See you there!! 😊
My mods will always be free. However if you'd like to support us, please plant a tree, say "thanks" in Posts, or support me on patreon.com/sammilucia 😊
Getting Help
Please report bugs in the Discord. We check here occasionally but the releases and support are a lot faster in the Discord 😊
Common Bugs and Fixes
Issues? Please let us know:
Please be excellent to each other 😊❤️
Is this normal behavior? If not any suggestions on what I can do?
Thanks again!
I have one question about using with GITS. In the recommended mods section you list the files to copy over but don't mention 'GITSHDR'. I assume we skip this one also? Just want to be sure.
I believe it's a vanilla bug though, as I took out all the mods and had it even fresh.
Image retention / overlay glitch recording
Is this with the new version of PTNext? So it is still there. Wanted to try new version, but seems like no need sadly.
I guess the next best version is PT21? Or is PT20 somehow more accurate/far-reaching at the insane preset?
it only happens occasionally. I haven't been able to fix it, so I assume a bug in CDPR's initialization of ReGIR (PTNext). remember, CDPR hasn't shipped ReGIR, I've force-enabled it.
however, many, many people use PTNext, which has a lot fewer lighting bugs.
For example, while in Badlands in Aldecaldos camp when I walked into the tent with stolen tank, I saw that glitch every time. Open/close menu - it is gone, walk out from the tent to campfire, then go back - and here it goes again...
It is less noticeable while doing some quest for awhile inside a building.
In average from my gameplay I noticed this like 5-10 times per hour.
And one more note: it can't be fixed while in photo mode... So if you set up everything and then noticed this glitch - well, it will be bad surprise for you.
https://www.youtube.com/watch?v=4rs5BiY67-c
Edit: Sorry idk why it sent so many times
Currently running on a 4060 8GB VRAM and AMD Ryzen 5 5600 Non-X Processor, 32GB DDR4 3200Mhz RAM, 1TB SSD.
I usually use DLSS and Frame Generation on Quality and no RayTracing/PathTracing, all maxed out, and get around 120 fps (80-60 real fps).
I try not to use Frame Reconstruction because it gets really blurry, grainy and the computer's interface becomes a ghosting mess.
i'd use PTNextV2 Fast or Medium, DLSS4 Transformer Balanced or Performance, and use the Frame Gen v3.8.1 DLL (it's faster). it should run great and look amazing
we've been using Ray Reconstruction Preset E ... i don't like the new presets (J, K)
with 8GB VRAM, i'd recommend reducing texture quality to 'Medium'
I'm impressed with the transformer model, but not with the new presets.
There is an unfixable vanilla CTD with PT or RT, especially reflections or lighting.
If you have CTDs while moving around in town related to this mod. Be aware, this mod is not necessarly the direct culprit, it reduces the time required to CTD but it will still happen on a non modded game after an undetermined amount of time in FEW locations, mostly japan and china town.
It is a problem with PT/RT, with the "phantom liberty" extension installed and some quests "triggered".
- A totally fresh save with PL START wont CTD, but after few hours ingame, some travels around and many calls received, it will start to crash when some quests are started. EVEN ON A NON MODDED GAME. RANDOMLY but AT SPECIFIC LOCATIONS, unrelated to power draw, OC, gpu load, it's either a bug in the code or memory management, it's not hardware. Loading a save with the correct conditions will CTD extremely fast, 5-10 mins. Without thoses conditions, the game wont CTD at all even after 12 hours non-stop!
- Without PL extension i believe that you wont be affected by this ctd even with reflection/lighting Rt/PT, but i could be wrong. I havent been able to reproduce it without PL, but i reproduced it many times with PL.
This mod, and many others will favorize the CTD, probably because of the increased burden on the memory management. But, for this specific crash, they arent faulty therefore they cannot be fixed.
Because of the difficulty to troubleshoot, the apparent but false relation to memory usage, the pseudo randomness and to disable graphic options reduces the chance to crash, many mods are falsely accused.
By disabling the mods, at first it may look like it's fixed, but it will happen again, later, at another spot, seemingly randomly. So dont waste time by bisecting mods:
If you dont have CTDs, you havent met the required combinaisons of time/quests triggered at the same time/locations. I hope you will be fine. When you get the CTD, try without PT/RT lighting reflection, do yours quests, then re enable thoses options much later and test again.
Still crashing? try RT off completely. While it happens less often without Reflection and lighting, the root cause is not Fixed and it can still crash. Mods altering RT behaviours, meshes, shadows, etc will favorize the crash.
On my own testing, i believe that HDD mode ON/auto may reduce the odds to ctd but cannot fix it, only RT off works 100%.
Still crashing without rt? It's another problem, either hardware, mod, oc or undocumented bug in the game, now you can bisect yours mods.
It seems unrelated to drivers, the first echoes of this ctd are from CP 2.12 or even older.
https://forums.cdprojektred.com/index.php?threads/ray-tracing-causing-the-game-to-crash-if-phantom-liberty-is-installed-on-2-10-2-11-or-2-12.11130028/
Another crash may happen at startup, because of the nvidia Ray reconstruction switch and a denoiser bug. This bug is related to ultra + but is easily fixable by disabling ray reconstruction in the config file of the game, then re enabling it ingame.
Unrelated but i put it there, Input loader may also CTD at start up if you modified it's files or some vanilla config, reinstall it properly by overwriting and it should be fine.
ULTRA + RT performance is lower than vanilla, i highly suggest to use the options only with PT. For RT you can use the mod without it's own config file and it will have some visual fixes with a slight loss of performance, for this, delete the config file of ultra+ and never touch the options. Dont even click on the "vanilla" or gpu VRAM stuff, or performance will be reduced on the next restart, with RT, and to fix it, you will need to delete the config file once again. I dont know why or how it happens, i only know that it's 100% reproductible and that the fps lost is major, 12%.
It shows. You are white knighting when i'm already trying to protect ultra plus from false accusations.
I'm not blaming ultra+, it's the opposite, i blame the original "vanilla" , unaltered, unmodded game. Thoses crashes arent driver related, nor hardware. It happens when there is an unidentified script, or quest, triggering. It breaks the save until you finish the quest, so driving around with the specific quest actived will crash randomly in few locations. Only with the DLC phantom liberty.
I'm warning players that, if they crash with ultra +, the real culprit could.... the BASE GAME with PL installed.
For thoses crashes, specifically, to reinstall the game does nothing, nor DDU, it's not related to hardware or drivers, and to use a save file that crashes on a new installation or different computer... will still crash, for this problem only. ( so if it's fixed by the above, your problem was different).
It's difficult to identificate, may take hours to CTD. Mods and mostly RT/PT reduce the time required to crash probably because of memory management. Crashing earlier, it would feel like thoses mods are the culprits, they arent.
When it takes 10 mins to ctd with mods. And 2 hours without mods... After 1 hour of testing without crash , it's human to believe that it is fixed, but it's not, it will just crash later.
Once the quests / scripts are cleared, the save wont crash anymore, even with the mods.
The config file is not even in the archive, it's created dynamically when you change settings on the UI. If you dont touch the UI, there wont be a config file. The mod uses the common.ini file and RT.ini if you have RT enabled in the options of the game, without the config file. It's purpose is to remember yours choices on the UI, enabling further changes, not to set up the mod for it's basics features.
Ultra + does most of it's work even without it. Yes, if you enable PT, you want this file (so it swaps to the version of pt of your choice). So i suggest that for RT because... you havent compared the RT FPS from native game to ultra plus RT with the option altered... but i did, it's lower by a lot. I'm not the only one to notice it. But ultra + has many benefits so it worths it to
CP with PL has some broken script or quest, that's it. Inducing a leak, that leads to CTD. More often with many mods and/or RT/PT, once the quest/script is ended, the save wont crash anymore. A new save, after a while, could encounter the bug at some point, but because it only crashes at some locations around japan and china town and also because it needs a lot of time for the CTD to happen without mods ( and even more without RT/PT), you may never notice it, you do yours quests and it's fixed on it's own.
I can go line by line "This mod, and many others will favorize the CTD, probably because of the increased burden on the memory management" and point out error after error or what doesn't make any sense, but that's not useful for either of us. There is no issue with Phantom Liberty installed. If this crash existed, the millions with PL would experience crashes, and don't. If you're CTD'ing in ten minutes, and still CTD'ing with no mods, you have a serious problem that is unrelated to Ultra+ and Phantom Liberty, most likely GPU or system wide instability, which is why I recommended what I did. That can be really frustrating, totally emphasize but again, pointing at the first thing that moves and yelling "there it is!" does not solve it. If you delete the config, nothing is applied until you re-apply it, which thereby defeats the purpose of the mod as it's not doing applying anything until manually intervene once again, unless you just constantly reapply it which.. doesn't make sense. Your problem is Phantom Liberty is more demanding and that's exposing your system instability- not memory leaks/broken scripts/quests/freshness of saves/ray recon being enabled on load/hdd mode (which is just lowering how demanding the game is and covering up your system instability- like diminishing graphics settings)/etc.
Again, I was not trying to be rude to you, but I think you are more interested in drawing your own conclusions than any advice or help, so- good luck with it.
And considering your answer, you still do not understand.
The crash is baked into the save, reproductible on other computers by transfering the save... It's very random and it takes a freakin long time. It's a leak, either script or quest related, graphic options (rt) and mods impact it greatly. You doubt it? whatever.
I have 0 crash, no CTD at all, on a "safe" save, with 100+ of mods. Graphic options, PT or RT, hdd mode off or on wont matter! Everything is fine!
It never happend without PL, but PL start will be bugged ( wont crash yet, just in a bugged state, so it has a relatively low chance to ctd) fast if you drive around for 5 hours , receiving calls without doing quests or interacting with the game in anyway. Then to ctd, you need to drive from china to japan town in circle constantly, it's exhausting, only few locations will crash, randomly. It crashes faster with hdd mode off and RT/PT and mods, which is a good way to test it. To disable RT /PT is also a good way to increase the time required to ctd, so we can do the quests and fix it for good, then re enable RT/PT. Oh and teleport/load screen prevents the CTD for a while, so it's necessary to DRIVE to both japan and china sectors.
A broken save gets fixed by doing some of the quests, i just dont have the time to spend atleast 40mins trials per quest done to verify which one is problematic. So indeed it's a pain in the ass to identify the problem.
Once fixed by doing the quests, it doesnt ctd anymore when reaching thoses specific locations in china and japan town. Other areas are crashless in my experience, and i didnt CTD in quests related locations.
The ultra +rt suggestion is not related to the crash, and no you dont miss much for the RT settings without the ultra+ config file. It's not even created until you click the UI. Ultra + auto detects RT mode from the game settings, you still get some fixes and RT changes, but you cant click on VRAM, the only setting that would matter for RT. Modifying the ultra + setting was never a part of it's installation (which creates the config file) and the original ultra+ settings are totally fine without the config file. Now, why does the config file applies changes that tank the FPS? good question.
Have a good day.
Model Transformer is hungry than Model CNN
do you have quests active? did you visit your appartment h10 if you have deceptious' mod & core quest? if not, go to your appartment once then try again.
instability is indeed known ctd /bsod reason, and both the bug i'm talking about and instability could happen at the same time, which is why i ruled out instability with many many tests and tentatives.
Just so you know, Sammi said that there is memory leak in 2.21, somewhere in the thread, such leak is not instability either and it could be related in a way or another, or not. Who knows.
For reference, I experience those when going to pacifica for the secret quest when getting back to Judy's after the mission in the power plant complex (trying my best not to spoil here).
However disabling ultra+ seems to fix it. I've been using the new transformer model.
And after tweaking around, looks like downgrading the cache accuracy from 100 to 50 (vanilla) fixed it for me. Seems pretty random, but if it can help, there it is !