Read From Location 000000c9 Caused an Access Violation.
Hot posts in thread: Crash on galaxy generation
-
Adam Solo Developer Ambassador 1000 Admiral
First-class! The issue was about some textures that were not in the right format allied with as well much memory beingness loaded at a single time (during the galaxy generation).
Looking forward for your thoughts!
-
Skillful news .... the second version of the special build yous sent worked! I tried in both windowed and total screen mode (full screen @1080p res) and it seems to be working fine. I'll have a run a risk to play more turns and dig into over the adjacent few days
Looking forward to it! Thank you!
-
Helpful x one
-
-
Adam Solo Developer Administrator Grand Admiral
Thanks for your help in solving this problem. So, it doesn't seem to exist lack of memory to run the game. DXD9 flags also didn't assist. Some people say that to exist a viable workaround in solving this kind of errors, but no luck there either.
No lack of disk space, drivers are updated, windows is updated. Worked in PA10 but doesn't work in PA11.
Nosotros did change the Unity version between PA10 and PA11, and I read that there seems to be issues with some Intel Hard disk drive cards running the game with more recent Unity versions (just not the latest). Something about the system not being able to load besides many textures at in one case, which can overwhelm your Intel HD 4400 retentiveness, or Unity isn't doing the same memory management information technology once did for some of those cards, or nosotros're now putting more than textures into memory at once than earlier.
The game does run in Intel HD cards. It runs on Intel HD 4000 and Intel HD 4600 but I don't take reports of people playing the game successfuly with an Intel HD 4400, like yours. It may be a local problem. Or, it may not and may be representative of a larger group of systems.
I run across 3 possibilities to try and solve this. At that place is a fourth, only I would not go in that location yet if we tin.
a) Moving to a new Unity engine version may solve the issue, and there are indications that it might.
b) We could endeavour to free up retentivity in the process of starting a game and so that not as much is allocated at once and possibly systems like yours can handle it improve that way.
c) We're currently working on farther optimizations to memory utilization, and that focuses in reducing texture sizes, so information technology's possible that this optimization chore may solve the issue, or at least bring us closer to solve it. These texture optimizations will be available in the next build, to be released soon.
d) Not preferred solution: - change textures to not use some properties we need for some cases (I call up this could technically solve information technology, just I feel it would be a workaround, so we should effort to first solve it with a), b) and c).
So, at the end I believe this is a memory management consequence, by Unity, the way we use textures and their sizes and quality, and something in the blazon of arrangement of yours that doesn't similar that. I'm positive that this will exist solved in the about future, and I suspect this type of mistake would show upwards much more in instance more people were exposed to the game at this stage.
And so, for the time existence I suggest we await for pick c). In the meantime, we'll discuss the possibility of sending a special build your way so we can endeavour option b) and encounter if we tin solve it by going in that road.
Thank you a lot for your time Mezmorki.
Last edited: Nov xviii, 2018 -
Welp - the same thing appears to be happening in the new version. Tried with the DXD9 flags also. I messed with some registry stuff to strength the power profile to max speed (apparently the Intel graphic are throttled back on the surface) to see if that helps. Still hangs during the galaxy generation processes. Patched windows once again. Also tried increasing my virtual memory and turning off as many background processes equally I could. Likewise tried seeing if I could classify more shared retentiveness to apply graphics in BIOS, only the MS surface is too locked down - no proper BIOS is accessible.
I looked at chore manager when it was frozen. ISG process was utilizing 4153mb of ram. I have 8gb of arrangement ram and it was at about 75% utilization. The CPU was also nonetheless cranking away at ~50% utilization on that task.
EDIT: On idle, with but chrome running, I have 5.five GB of system memory costless according to task managing director.
Hopefully some of that helps.
I'm happy to test new executables if you want to try things without having to event a full new release.
Thanks,
Attached Files:
-
Adam Solo Programmer Ambassador Grand Admiral
I think the trouble may be lack of retentiveness to run the game.
Analysing one of your crash reports I see this:
ISG [version: Unity 2017.4.3f1 (21ae32b5a9cb)]d3d11.dll caused an Access Violation (0xc0000005)
in module d3d11.dll at 0033:7ac61634.Mistake occurred at 2018-11-04_072744.
C:\Games\Interstellar Space Genesis\ISG_pre-alpha_11_unstable_64bit.exe, run by kiley_000.
82% memory in utilize.
8113 MB physical memory [1418 MB free].
10824 MB paging file [1573 MB free].
134217728 MB user address space [134208310 MB gratuitous].
Read from location 000000c9 acquired an access violation.
And then, judging from the values above, it seems yous had 1.4GB RAM available physical RAM plus 1.5GB from disk paging file (disk space), for a full of around 3GB of available retentivity. PA11 Unstable took around four.5GB of RAM to run the game, between VRAM (graphics card) and RAM (residuum of the game's data). I saw yous had 8GB of RAM in your organization but didn't check that you had nearly all RAM in apply by other processes.Now, PA11 Unstable Hotfix should be taking effectually iii.0 to 4.0GB of retention, depending on the operating system and video carte installed. Then, if nothing has changed you'll probably still become a crash with those numbers. However, if you try to free up some disk space or try not to have as many processes consuming RAM on your system I think yous'll have plenty combined memory to run the game.
Let us know how it went.
-
Concur x one
-
-
Adam Solo Developer Administrator Grand Admiral
Allow us know if the hotfix has solved the issue in your Surface Pro. If not, please transport the states the output_log.txt. Thanks!
-
Cheers
Yes - I'chiliad fine playing information technology on my main machine for the fourth dimension being. Mostly want to become it running on the MS Surface as a means of helping you all to squash a potential issues that might pop up on other peoples' systems likewise.
Windows is completely up to appointment.
I do have some feedback I've been jotting down as I play. Generally UI related suggestions that this point.
-
Helpful x 1
-
-
Adam Solo Programmer Administrator Grand Admiral
Too bad. Thanks for trying. We doubtable the fault may be related to memory requirements. I have an Intel HD 4000 and 4600 in two different systems, and they both work although the commuter version is much different (lower) from yours (10.18.x.4358 here, while you lot had 20. something). Nosotros know of other players playing with Intel Hard disk cards, so it must be something specific in your arrangement.
Nosotros did a huge memory optimization to the game and the new version will also have slightly different graphic settings. We're going to allow the system to choose the all-time graphical API possible instead of forcing the organisation to utilize DirectX xi. The hotfix will be available very soon (nosotros await to release in a few days tops).
If that does not work nosotros'll try something else.
Do you take your windows updated? I read that having an outdated windows may also cause problems with drivers. I know I had issues with my integrated carte du jour (Intel Hard disk 4000) in the by with dual monitor support and when playing youtube videos (the system would crash when watching videos in fullscreen).
Don't worry Mezmorki, nosotros'll sort it out. Thanks for your patience. I know y'all can play in another organization but we'll do our all-time to support you lot in playing the game in your surface pro.
Looking forrard to read your impressions on PA11.
-
I tried with the -force-d3d9 flags and it still crashes.
The graphics card is an Intel HD 4400. This is a MS Surface Pro ii (first release version).
I tried in vein to gyre back my graphics drivers. Windows doesn't have a tape of prior versions beingness installed that I tin can roll back to. I tried downloading and running a bunch of earlier driver packages but none of the stock Intel drivers manifestly employ or work on the MS Surface. They kept giving installation errors or were redistricted from beingness installed outright.
-
Adam Solo Developer Administrator Thousand Admiral
The file downloaded through space sector is the aforementioned installer.
Analysing the logs with and without the actress d3d flags seemed to have produced the aforementioned results. So, information technology's something else.
Could yous try with this flag -force-d3d9
\Edit What'southward your graphics card model?
\Edit2: By the style, I have an Intel Hard disk drive 4000 integrated graphics menu that runs the game fine (your card is also of the Intel Hard disk drive family). And, my Intel Hd 4000 drivers are quite old (21/12/2015 driver version 10.18.10.4358). I have the latest updates of Windows 10 though, can yous check you also have Win10 updated on your side? This seems to be a system related issue, involving your menu's specific model, drivers (old or new) or the fact Windows may not be upward to engagement. Let united states of america know how it went with -strength-d3d9
\Edit3: Too, if it's not too much to ask, and the in a higher place doesn't solve the consequence, could I ask that you lot rollback your Intel HD graphics carte du jour drivers? You could but update later and that will give us a flake more information to piece of work with regarding the Intel HD bill of fare family. I ask this of you because I saw a much older driver for the Intel HD family in 2 computers I have access (around x.18.x.4358), while I see you take version twenty.19.15.4331 Usually latest is amend but with Windows updating stuff regularly and knowing how the Intel HD family has caused me bug in the by it would exist worth a try, in my opinion. Thanks.
-
Here's the crash files and output log with the extra flags.
I'm going to effort uninstalling and reinstalling. Is there a non humble bundle version that can exist downloaded all the same?
EDIT: looks like the file downloaded through infinite sector is the same installer?
EDIT2: Reinstalled + cleaned out old files. Same problem.
Fastened Files:
-
Helpful 10 1
-
Adam Solo Developer Administrator Chiliad Admiral
Ok, thanks. The error with the forced OpenGL was kind of expected, just wanted to confirm.
The output log I see in your latest attachment is from running with the OpenGL forcing. Could yous send an output_log.txt when running with the flags of the 2d pick, only to check if something was unlike when using those flags?
The crash seems to be near trying to read from or write to a virtual address for which the game has no appropriate access.
I understand from reading in several places that it is common to have these kinds of errors if your Windows is not upwards to date. Could that exist the issue?
-
No luck on modifying the command line strings. With opengl way, I get an immediate windows error "InitializeEngineGraphics failed"
With the second selection, the game launches fine but crashes immediately at the start of the galaxy generation process.
Fastened are the log files from that, including newest output log file
Attached Files:
-
Here's the output log file.
The drivers are already upwardly to appointment. I re-ran intel's driver update tools and it said at that place are no newer versions.
I'll effort running in GL mode next. Cheers
Attached Files:
-
Adam Solo Developer Administrator Grand Admiral
If updating the graphics card drivers doesn't solve it endeavor to strength open gl mode. Right click on the game'southward shortcut icon and add the following to the Target. The -force-opengl line must come later on the executable path like this:
Example: "<your_path_here>\ISG_pre-alpha_11_unstable_64bit.exe" -force-opengl
If that fails or doesn't solve information technology, try this:
"<your_path_here>\ISG_pre-alpha_11_unstable_64bit.exe" -strength-d3d11 -force-gfx-straight -strength-d3d11-no-singlethreaded -force-feature-level-11-0
Let us know.
-
Adam Solo Developer Administrator Grand Admiral
We'll look into this. Thank you for the log files.
In the meantime, could y'all send us the output_log.txt file on your Surface Pro? The log can be constitute in C:\Users\<yourusername>\AppData\LocalLow\Praxis Games\ISG\
Cheers!
\Edit: Could you likewise endeavour and update your graphics card driver to see if the problem persists?
-
I was playing ISG previously on an MS surface pro.
With Alpha 11 it crashed everytime I tried to launch a new game during the galaxy generation process the progress bar stops about fifty% of the mode across and I go an error message in windows and the game crashed.
Beneath are three different error logs.
I was able to get the run running but fine on my main computer. No technical issues so far.
Attached Files:
- Close Menu
- Home
- Forums
- Search Forums
- Contempo Posts
- Members
- Notable Members
- Registered Members
- Current Visitors
- Recent Activity
- New Profile Posts
- ISG Site
- FAQ
- Buy Now
- Newsletter
- Wiki
- Search
Source: https://www.interstellarspacegame.com/forums/index.php?threads%2Fcrash-on-galaxy-generation.755%2Fhot-posts
0 Response to "Read From Location 000000c9 Caused an Access Violation."
Postar um comentário