Pixinger

It seems that the issue is not as random as we first thought. We did a little of testing and observed the following: If there are two different flights on deck (lets say: Chevy and Uzi) and one of Chevy planes takes a catapult, the complete Uzi-Flight is blocked on all catapults. This block stays until the complete Chevy flight has departed from the carrier (only occupied Chevy slots count). Right after the last Chevy launch, Uzi is free to use the catapults again. That behaviour was reproduceable consistently - at least in our mission/server. The first plane seems to block for it's complete flight. Maybe this observation helps some people to organize work around this issue. For coordinated events this is not a big issue, as the departure is "coordinated". How ever in freeflight missions during the week, it can be annoying. Maybe a simple workaround would be to split the 4 ship flights into seperate groups, although I haven't tested this. It could be that this allows only one launch after another. I like to mention, that this are just some observations. Maybe there is more to it, maybe we are wrong about it. I just thought it's worth sharing this... happy flying! Update: I tested the workaround with "single groups" . Of course it makes the problem worse, as only single departures are possible then...

Is there experience with Intel i5 CPU with embedded HD2000? Or maybe i7? According to the manual you can increase memory up to 512MB? Wouldn't this be enough?