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
Computer Information:
Manufacturer: Gigabyte Technology Co., Ltd.
Model: B250M-D3H
Form Factor: Desktop
No Touch Input Detected
Processor Information:
CPU Vendor: GenuineIntel
CPU Brand: Intel(R) Core(TM) i5-7400 CPU @ 3.00GHz
CPU Family: 0x6
CPU Model: 0x9e
CPU Stepping: 0x9
CPU Type: 0x0
Speed: 3000 Mhz
4 logical processors
4 physical processors
HyperThreading: Unsupported
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 GTX 1060 6GB
DirectX Driver Name: nvldumd.dll
Driver Version: 31.0.15.1659
DirectX Driver Version: 31.0.15.1659
Driver Date: 6 23 2022
OpenGL Version: 4.6
Desktop Color Depth: 32 bits per pixel
Monitor Refresh Rate: 60 Hz
DirectX Card: NVIDIA GeForce GTX 1060 6GB
VendorID: 0x10de
DeviceID: 0x1c03
Revision: 0xa1
Number of Monitors: 1
Number of Logical Video Cards: 1
No SLI or Crossfire Detected
Primary Display Resolution: 1920 x 1080
Desktop Resolution: 1920 x 1080
Primary Display Size: 20.75" x 11.65" (23.78" diag)
52.7cm x 29.6cm (60.4cm diag)
Primary Bus: PCI Express 16x
Primary VRAM: 6143 MB
Supported MSAA Modes: 2x 4x 8x
Sound card:
Audio device: Headphones (HY22 Stereo)
Memory:
RAM: 8152 MB
VR Hardware:
VR Headset: None detected
Miscellaneous:
UI Language: English
Media Type: Undetermined
Total Hard Disk Space Available: 1067003 MB
Largest Free Hard Disk Block: 245103 MB
OS Install Date: Jul 29 2020
Game Controller: None detected
MAC Address hash: 52c86b27a4ef159512fe05fb3d71e346dcd5f601
Storage:
Disk serial number hash: 8d83d800
Number of SSDs: 1
SSD sizes: 120G
Number of HDDs: 1
HDD sizes: 1000G
Download DX11 again here: https://www.microsoft.com/en-us/download/details.aspx?id=35
You might need to verify also. It may or may not work, DX errors are pretty general.
2. Does this happen (and you need to test this in this order): On an official The Island Server? Single player The Island map? Or only on the map and conditions you specify in your posts above? Test these because it helps narrow down the issue.
3. Be aware that your 1060 graphics card is not meant to play the game in the highest graphic settings. Make sure you're playing at the recommended settings for that card and not above it. Use nvidia geforce experience program to detect and set the recommended settings. However be aware if you are playing with adjusted play settings with boosted rates/speeds, mall sized bases and dino lots etc, then you'll need to adjust down your graphic fidelity settings to not sacrifice performance further.
4. Do not use msi after burner, the nvidia geforce experience in game overlay feature(gne itself is ok), overlock etc. Those can also add to issues.
Try those and report back.
2)it happens after 374.1 patch came out
3) i tried from low to high ,same issue
4)i dont think that affects because i been playing with msi afterburner ,i only experience some lag thats it
1. Your error reports "array out of bounds". I explained that that specific error has certain conditions with in game play that has caused it in the past:
-- 1.Using climbing picks/equipped that are broken and need to be repairs.
--2. Hazmat suit similarly broken needing repair.
--- 3. 1 and 2 but in inventory and not equipped.
----4. 1-3 due to being on the Aberration map.
-----5. 1-3 but on other maps OR other similar broken item conditions on same or other maps(again this one is rare).
2. Patch point is not relevant. I asked you to test specific server map play to see if you get the ===Exact=== same crash. If you do not wish to test this then it makes it harder to narrow down the conditions regarding your specific Array out of bounds issue.
However you seem to not be interested in testing things properly so good luck to you.
3. That is yet again not what was asked for you to do. Your graphics card has specific settings recommendations. Setting it to that so you can test and eliminate it as a possible issue source correctly was the point. I then added a warning that if you were playing outside of the normal default boundaries and expectations for playing the game, that it would have to be lower.
However, you seem to not be interested in testing things properly so good luck to you.
4. If you keep on using msi afterburner, good luck to you it is a known issue maker and by ignoring that it could be a contributing factor.
5. Also and I almost missed this that you said:
" -no mods except server mods from unofficial"
If you're experiencing this issue while you play on unofficial servers, then those mods would be relevant and should be listed by name and in their load order.
6. Also I missed this initially and its not issue related but more or less to help you understand things. The listing of the code has nothing to do with you playing lost island. Its just how the developers are organizing the code. We see things change throughout the year and in the past its even been with event naming instead too when issues had nothing do to with an event.
Keeping in mind you piggy backed onto someone else thread where you also cited a ---different error code report-- than the array out of bounds one above, this should help show you that there are things you do not understand from these reports and IF you are continuing to crash and the error reports are different, that needs to be reported. Linker load is not the same as array index out of bounds for example.
So basically you've come to the forums, asked for help then are refusing to test to sort things and refusing to stop doing things to be known issue makers.
Sorry but that means you're kind of not really making it easier to help you source your specific variables of issues to help you find possible solutions.
So again good luck to you.....
if you say the array bound is the cause then its is their end game issue .i really dont know
we are not seeing one person ,but multiple players having that exact lost island breaking issue .That could be a patch ISSUE not PC ISSUE
When you say i refuse to do the test ,there are people who had done things they were asked and still the same .How many are they working ?
I already reinstall the game as mention
please dont use my graphic card as a hit to say its outdated and blame on it .
my graphic cards may not be as good as 3000 series but definately wont break gameslike this ARK
I ll definately ignore you because you tend to protect the devs and pushing the blame of making me harder
I get why you feel so. You don't keep your computer's drivers up to date, you play beyond the means of the rig, you don't follow directions to test accurately to help source your issues, you use moded content and then do not list mods which can be a contributing factor . And you jump onto other people's threads saying you have the same issue as they do when your crash error reports have -nothing- to do with their issues.
Crash reports are symptoms, not causes. Crash error reports can in not a small number of cases have multiple variables and sources. That's why getting accurate and detailed information is important.
You failed to do most anything to help you sort it and by all accounts you did this by choice/intentionally ignore things.
Sorry but you chose not really help make it easy to help you and at this point its best to say its a user end issue predominantly.
Nothing more really needing to be said except, truly, good luck to you.