Space Engineers

Space Engineers

Advanced Liftoff Control
Iye  [developer] 3 Mar, 2016 @ 2:07pm
Bug Reports
Post all bugs you find here
< >
Showing 1-9 of 9 comments
Chuck 17 Mar, 2016 @ 4:55am 
"Caught error during execution of script: Object reference not set to an instance of an object".

Usually from my experience that means that the script is calling a block that doesn't exist? But I triple checked the names, and even copy pasted to make sure the names on blocks were EXACTLY as specified in the script. I also noted that your script is designed to catch such problems and produce a message if it can't find a necessary block. On a hunch I deleted all but one remote control block, but that didnt help. Not sure what the problem is.
Iye  [developer] 17 Mar, 2016 @ 5:39am 
Originally posted by Chuck:
"Caught error during execution of script: Object reference not set to an instance of an object".
hm. i thought i took care of all of those........


//edit Iye:
just did an update (no version change) and it should work now
Last edited by Iye; 17 Mar, 2016 @ 10:47am
Chuck 19 Mar, 2016 @ 7:25pm 
Well that explains it. I was wondering if I did something different, because it works now. Wow, thanks a ton; great script!!
Arcane Axiom 7 Mar, 2017 @ 3:54pm 
Ah, commented in the main thread before I saw this.
I'm getting NREs as well; just downloaded the script a few days ago.
Last edited by Arcane Axiom; 7 Mar, 2017 @ 3:54pm
Iye  [developer] 8 Mar, 2017 @ 1:35pm 
@sean47933 ive just tested in dev branch, and it works fine. However, it seems that the autogenerate feature for thrusters no longer works. (looks like keen changed how the (Up) is actually not a part of the name anymore).

Yet the script doesnt throw any error for me. Do you have a timer setup with the correct name? Because thats actually the only thing that may throw an errorl.
Arcane Axiom 8 Mar, 2017 @ 3:49pm 
Nope. Vanilla world, base settings for your script except autoGenerate = 0, all blocks and groups named appropriately and even visible in terminal. Owner set to "me" on everything. Still get an NRE.

Update: Wat. Your example ship works fine.

Update 2: See below screenshot. about as simple as can be, using the exact script from your example ship; still no dice.
https://steamhost.cn/steamcommunity_com/sharedfiles/filedetails/?id=879707495

Update 3: Peppered the script with debug logging; exactly 0 of it is getting to the debug display. Which tells me the script is failing before it even takes off (pun *entirely* intended).

Update 4: I would unit test this ♥♥♥♥, if the assemblies would even build. As it stands, it's complaining about something that probably has to do with my AMD processor. :/
Last edited by Arcane Axiom; 8 Mar, 2017 @ 4:50pm
Iye  [developer] 9 Mar, 2017 @ 12:30pm 
Usually those null references have 2 major options to pop up, it either tries to access a block that does not exist (i'm fairly sure my script is fully secured against those), or its trying to access a field that does not exist (obviously not happening since the example ship works)

Looking at your screenshot leads me to assume that i ♥♥♥♥♥♥ up the displays somewhere though, because i tested it yesterday with a pretty much identical ship, however mine had all displays.

Try and run it with the argument "INIT" argument and see what you get. (on all 3 displays and in the echo area).
Arcane Axiom 9 Mar, 2017 @ 2:24pm 
Holy Kittyhawk, Batman!
All 3 LCDs must exist :)
Iye  [developer] 9 Mar, 2017 @ 3:33pm 
Oh well. I just figured....

My local development version has that bug in the WriteOut() routine fixed since ages. I probably forgot to upload :P

Problem is my version has an error where it inists on the existance of atmospherics.... :P
Ill work on that this WE and fix it. Hopefully.
< >
Showing 1-9 of 9 comments
Per page: 1530 50