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
great script, btw.
Great script, by the way
Add it to the info displayed, pls.
Also, maybe a warning: "Ship mass changed by more than 10% since last computation"
int PBScreenNumber = 0;
int ControllerScreenNumber = 0;
It seems to have a problem with the Remote Control Block, as far as i can tell it doesn't work when the ship already has it on the grid. If you try to load the script or recompile it when the block is already on the grid it creates this issue (for me), but this is just from my own investigation. I suggest fiddling with all the settings and getting everything compiled before adding the control block to avoid problems, i will correct this is the problem reoccurs.
so not high on his list of things to do
u trying on SD expanse or other?
Caught exception during execution of script:Object reference not set to an instance of an object.
at Program.InstanceCheck()
at Program..ctor()
I'll try to fit it in.
Unfortunately the orbit command still dosent work at all:
The orbit command dosent stop when the orbit is reached. It just says
Error:
No gravity field detected. Unable to initiate orbit sequence
I need to look into the PB locking up.
The script also bricks the PB upon setup most of the time, forcing me to delete the PB itself as the block won't even perform other scripts anymore.
Is there any fix to these issues?
On a separate grid, I had the same issue as Tipp. Same crash, same stack trace.