linuxgurugamer

That's from Janitor's Closet

Sorry @Me1_baseI was probably mixing my words up, yes correct, the plugin defines the additional values FAR uses as you know doubt already know and then FAR does its voxel stuff to make it all work nicely. Sorry for any confusion @HebaruSanI looked a few pages back, I can see you highlighted the issue. I do remember you being in contact all that time ago. Unfortunately RL got in the way (I got diagnosed with early stage cancer so I had to drop off the radar to get myself sorted - all better now). Now that @linuxgurugamer is getting us altogether it would be good to touch base in

That log only gets to the main menu, please get in flight and try that, then post the log

You can also use this:

Oh sorry. I was going on the recent comments that FAR wasn't a dependency Maybe it's ripe for an adoption? I will look into creating the organization you suggested

@Jebman82 @Daniel Prates I've changed the NETKan file so that FAR isn't a dependency

If you have a 4 minute burn, you should start 2 minutes BEFORE the node

Install with CKAN and then delete the FAR directory

Lights are either off or on. Every time something else gets added, it adds complexity and overhead

that's the latest I am interested in any exceptions which you see with it

Next beta will have the KuddleKorner lights going on automatically when two kerbals (male & female) are inside

Respectfully, when it comes to scientific research, it's impossible to say what is missed by delays like that. On paper it looks good, but going cheap on R&D has caused numerous issues over time.

I did a minor update to EvaFollower the other day when I saw your log, are you using it?

On the other hand, with things like this, you could send 10 probes and suffer 100% loss because of an overlooked issue which would have been revealed with more R&D.

Looks like this got posted in the wrong thread