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
Best way (for me) to deal with it: Take several missions in the same system, as inter system jumps don't seem to cause the crashes. I collect 4-6 missions of any type in a system and then do em.
before 4.0, this was around 4 to 5 warps, now it's between 4 to 8 warps...
No work around cause i think it's a memory laek accumaled at each warp...
It's very frustrating since it occures too often...
The only actual thing to do is saving before each warp....
I hope DBK ad an auto save before warping like he does each time you enter a stellar system with a portal...
Do you get the bug reports about this? I have been hitting the "send and restart" button every time.
As a fellow developer:
I can not see the debug stuff, but the Error text suggests EITHER a silly out of bounds error (unlikely, but I have seen worse and more missleading error texts that got fixed by that lol), OR a threading missmatch (way more likely).
If it is a threading issue, and since it does not happen all the time, I think it could be two treads working on a task and needing the results to finish the warp. If one thread is slower or they just don't line up correctly (Java has this issue a lot... not sure if c or c# also have this, as I have not had this in c# yet)... then it would crash with a similar error message.
Basically: Make sure the results are finished, before you use them. This can be done in two ways....
1. The cleaner approach with a light overhead: Outsource the needed calculation results to its own model. Let's say "WarpFinishModel" and call a "OnChanged" event. When all results are in, this OnChangedEvent would finish warp.
2. The more dirty, but quick and without Overhead approach: Have all threads implement a "wait for the other threads" option activated, so while all stuff gets multithreaded, no thread is issuing the "Warp finished" call, before all the other threads are done as well. Basically making sure all calculations are done as well.
I know, this is just a very wild guess, but I have seen these kinda problems in many languages on a lot of different projects,... so just have a quick glance over the code if this is a possible issue / solution combo.
Its just too annoying.