If you can play with this "workaround" then... have fun with the game now.
In the meantime i try to find the problem. First i must find the function which produces this high CPU load. Then i can examine this function and then it's possible that i can make a solution... maybe.
Luke wrote: BTW, cant await the german version, crossing fingers best
Well, our dev team have the slogan "Wir ziehen das durch, geht nicht gibts nicht!". And we don't want to make a "simple" translation, we want to make a very good translation with some improvements. This cost lot of time and work, please have patience.
I have a assumption, so i wrote you a little tool (launcher). You have a really weak CPU and it seems this is the problem. This tool forces Windows to run the WCS engine on both of your CPU cores, not only on one core.
This is NO solution, it can be maximum a WORKAROUND! If this works... not sure yet, try it.
Simply start the launcher. There is no need for copying the launcher into your WCS program folder, but you can, if you wish.
Sorry for the late response, thx a lot for the tool. In fact I could not see a difference launching with two cores, have the same problem of game or even system crash. What is really wired is the fact that WCS is working on a eee pc which has even half of the performacne power (dumpy on asteroid missions, but no crashs)
I spent some time the last 2 days for investigate this issue and what i found are only bad news! It seems that there are massive problems with FSO games and Intel graphics. The Diaspora team wrote under requirements: