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
The bigger problem might be mods which conflict with each other, or mods which have not been updated in a long time and may have been broken by a more recent update to the game. For example, I notice you have a few mods there which add new dinos - might it be possible that two of those try to add a creature which has the same name as each other, and so the game can't figure out which creature is which and crashes because of that? And a couple of the mods on that list haven't had updates for a few years - Dino Colourizer hasn't been updated since 2019.
Not saying that those things I mentioned are the cause of your issues, they might not be a problem at all. But it's a possibility.
To find out for sure, you might have to do some testing. Take a backup of your single player world and save it somewhere else on your computer, so you have it safe and sound if anything goes wrong. Then, try removing one of the mods on that list, and loading into the world. See if it crashes without that mod installed. If you still get a crash, restore the save from your backup and remove a second mod from the list. Try loading the game again.
Keep doing this until your game loads smoothly. When it does finally work, you'll know that the last mod you removed, whichever one that was, is causing the trouble. Perhaps it is outdated and so you would need to drop it from your game entirely, or maybe it is conflicting with another mod so you can try that offending mod on it's own and see if it still crashes without any other mods installed. By swapping them in and out like that, you should be able to track down the issue and get it sorted permanently.
Crashes are symptoms and not causes and while mod load order can be one factor, your use of abandoned and potentially broken mods that havent been taken care of as far back as 6 years ago by the mod maker may also be a factor.
Also your rig may have discrepancies or in conjunction with the above be a mutually inclusive factor. If you go to the steam help menu, click system information, and then copy paste all that here we can then see what steam detects for the comp and any potential discrepancies that may have relevance.
Thank you for responding! I will try your advice and come back with more information very soon.
Thanks for you response! Here's my system information, I hope I pasted the right stuff.
Computer Information:
Manufacturer: Inet_AB
Model: System Product Name
Form Factor: Desktop
No Touch Input Detected
Processor Information:
CPU Vendor: GenuineIntel
CPU Brand: Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz
CPU Family: 0x6
CPU Model: 0x9e
CPU Stepping: 0xa
CPU Type: 0x0
Speed: 3696 MHz
12 logical processors
6 physical processors
Hyper-threading: Supported
FCMOV: Supported
SSE2: Supported
SSE3: Supported
SSSE3: Supported
SSE4a: Unsupported
SSE41: Supported
SSE42: Supported
AES: Supported
AVX: Supported
AVX2: Supported
AVX512F: Unsupported
AVX512PF: Unsupported
AVX512ER: Unsupported
AVX512CD: Unsupported
AVX512VNNI: Unsupported
SHA: Unsupported
CMPXCHG16B: Supported
LAHF/SAHF: Supported
PrefetchW: Unsupported
Operating System Version:
Windows 10 (64 bit)
NTFS: Supported
Crypto Provider Codes: Supported 311 0x0 0x0 0x0
Video Card:
Driver: NVIDIA GeForce RTX 2070 SUPER
DirectX Driver Name: nvldumd.dll
Driver Version: 31.0.15.2756
DirectX Driver Version: 31.0.15.2756
Driver Date: 12 5 2022
OpenGL Version: 4.6
Desktop Color Depth: 32 bits per pixel
Monitor Refresh Rate: 59 Hz
DirectX Card: NVIDIA GeForce RTX 2070 SUPER
VendorID: 0x10de
DeviceID: 0x1e84
Revision: 0xa1
Number of Monitors: 2
Number of Logical Video Cards: 2
No SLI or Crossfire Detected
Primary Display Resolution: 1200 x 1920
Desktop Resolution: 3120 x 1920
Primary Display Size: 12.76" x 20.39" (24.02" diag), 32.4cm x 51.8cm (61.0cm diag)
Primary Bus: PCI Express 4x
Primary VRAM: 8191 MB
Supported MSAA Modes: 2x 4x 8x
Sound card:
Audio device: Speakers (High Definition Audio
Memory:
RAM: 16299 Mb
VR Hardware:
VR Headset: None detected
Miscellaneous:
UI Language: English
Media Type: Undetermined
Total Hard Disk Space Available: 2384086 MB
Largest Free Hard Disk Block: 735274 MB
OS Install Date: jun 04 2023
Game Controller: None detected
MAC Address hash: a48b0759b4c587c9f639c3bb03bcaa723a578126
Storage:
Disk serial number hash: e90f0a19
Number of SSDs: 1
SSD sizes: 500G
Number of HDDs: 1
HDD sizes: 2000G
Number of removable drives: 0
1. Driver Date: 12 5 2022
You've not updated your graphic card in over a year. In gaming that's a no no. Go to the nvidia website and download the nvidia geforce experience program if you havent already. Not only does it help keep you informed on updates needed for your card, it also can give you the recommended setting for playing games like ark.
2. Number of Monitors: 2
Number of Logical Video Cards: 2
Primary Display Resolution: 1200 x 1920
Desktop Resolution: 3120 x 1920
Ark tends to have issues in resolution settings above 1900 x ---- ranges. Drop to 1 monitor and set both your primary and desktop settings to match in a resolution withing the 1900 x ---- range limitations at least.
3. Also be aware that if you're playing ark on an HDD and not the SSD, load times into the game will be long, especially if you're in single player and then -exponentially- longer with mods(and the size of the mods). While this isnt necessarily a cause, it is something to keep in mind that may have slight relevance.
Overall, your poor mod management/choices are the primary cause candidate, yes, but due to your also not keeping up to date with your driver and more appropriate resolution settings, it can also be a recipe of all that and not mutually exclusive.
Best of luck.
Add half the mods, see if you crash.
while cant add all mods
If crash remove the last mod and try again
else add half of the remaining mods and try again.
Speaking as a general diagnostic consideration:
Typically if someone is attempting to narrow down mods as a source, you dont "add half" you tend to add each incrementally so as to better have a chance to narrow down possibilities.
However it doesnt account for:
1. Load order potential causes
2. Combination mods (ie 2 mods on their own may be ok but 2 together may not due to conflicts and hermit also touched upon that.
3. Neglecting any other rig specific contributions. (If a rig isn't kept well as it should or if the rig isn't capable of handling the demand of x mount of mod use).
and more....
But the main point is that mod testing/adding should be again one at a time instead of bulk amounts as it would obscure whether a specific mod itself (or combo conflict) are compelling culprits.
When you add / remove 1, you search in O(n) time.
Yes I was lazy above, but once you figure out why this is clever, you can fix that error.
I think most readers can more logically just understand why this is inane per what I mentioned above. The only thing being expeditiously learned from what you just wrote is that you're being (again as this isnt the first time) intentionally silly.