Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
My impression is that the game does run stable for the vast majority of players (otherwise we would see this discussed much more often), so the cause is probably either a very rare hard- or software condition, or our systems have an inherent instability that Pacific Drive happens to trigger. Feel free to take a look at my profile if you want to check for similarities in our setups.
2) Then describe in detail how the error appears, after how much time etc
3) Are there no overheating of components, have you ever overclocked them.
4) Have you ever Testmem5 (1usmus v3 config) one test cycle?
5) If you are playing a game based on Unreal Engine 4-5 (any game) and you suddenly start getting errors like: D3DDevice HUNG; D3DDevice LOST;
'Out of video memory' (first of all on GPUs on which for obvious reasons it simply can not be)
then for starters, I recommend setting the OS swap file size to FIXED SIZE 32 GB (this means that when setting 'Custom Size' -> 'Initial Size' and 'Maximum size' must be the same -> 32768). The paging file must be on the SSD (system partition C:). It is advisable to have at least 32 GB of physical RAM.
Here, the problems will not be in Pacific Drive, but in Unreal 4, on which the game is built, the thing is that this game engine loves a lot of RAM and, oddly enough, large swap files.
First link from Google (do not download any files, just a picture for visual aid)
https://www.thewindowsclub.com/increase-page-file-size-virtual-memory-windows
PS This is how Unreal Engine error looks like when you ran out of RAM and there was not enough reserve for swapfile. (or swapfile was turned off). And you need to use it in FIXED mode.
Also it sometimes happens that such an error occurs even if you have 64GB of physical RAM, and after adding a small 16GB swapfile the problem disappears.
PSS And if all this doesn't help, the next step is to disable Resizable BAR in BIOS.
I'm unable to progress to Sierram since everytime I try to travel there I got crash on PenDrivePro. I sometimes also got the crash when traveling to different junkction.
From crash logs I assume there is some problem with specific asset that is 100% at Sierrarm and random at other ones.
Crash seems to occured after the save is done so everytime I got the crash I can also delete the save as well. If I try to load it - crash again. Therefore I'm currently playing at 3 save all the time.
I've emailed the support with logs and dump and I'm waiting for some sort of solution.. Checked all the drivers and all of them seems to be up to date.
Isn't "PenDriverPro" just part of the game save path ?
Like what I mean is this is the dictionary path the game uses for your save files:
C:/Users/Your Username/AppData/Local/PenDriverPro/Saved
So if your getting an error message referencing "PenDriverPro" then isn't that just the Unreal Engine Error Reporter kinda just telling you it encountered an issue saving the game ? - or am i just misunderstanding how the UE Error Reporter tool works ?