i wish this was a feature in the main game, we absolutely need it and things like educational tours. i had a good time with this script running in the background of my home on the TV. fantastic.

Thanks for the positive comments. This script is not sustained since 3years, it is a miracle that some part of it is still working after all those updates. I WONT UPDATE THIS SCRIPT because its an absolute mess, i dont have time ,energy and motivation to get back in it. Most of the bugs that appears randomly and stopping the script may be solved by lowering the parameter "search speed process", which directly rules how fast the script is reading logs and writing stuff.

The script is a must. But I dont know sometime it just doesnt work. I checked the console it always stop at "selectobject type" and then nothing happen. Please fix it, bro. This Script is a life saver to the community!!

try to decrease "search process speed" balue it mights help for your issues.

The script is fantastic! Only issue is sometimes it will attempt to fly through a planet it has just visited causing the script to loop on the same planet. Continuously approaching it, orbiting it, and then flying through it when trying to find the next one. Also the occasional location error which completely breaks the script

@gamezoone
"Search proscess speed
Decrasing the slider will make the search process slower. It can help to prevent menu respawn while searching for planet or stars if you frequently suffer of it with default settings (95)."

Yo lo configure a 75 y funcionó

I set it to 75 and it worked
(translated with Google)

Is it going to be any update? With the latest update of SE the script randomly stops with the error location could not be found.

its literally obsessed with moons :/

I SAVED ONE OF MY FAVORITE LOCATION 'BLACK HOLE' but when i choose 'mixed random and saved place' and then once explore bot goes to black hole sulface, it cant escape its sulface itself.. :(
how i can only watch black holes with planet sulface? except black hole sulface.

It has been planned, but turned technically quite impossible. because object are too close to each other comparated to the default acceleration scripted. You can still try to save each planet of the system and use the saved place mode. But the script isn't up-to-date and i'm afraid it won't works with our system in the milky way (milky way adress wee hardcoded there's amny update before, and is not up-to-date).

is it possible to make it tour only one star system? I would like it to tour all the planets and moons in our system, but I can't figure out how.

As long as you found the SEB folder you should find an executable "SEB.exe" inside. It's an Autohotkey script. To be exhaustve you should find 3 folders, a readme, and the executable. If the exe is not there, it could be your anti-virus but to be honest i'd be as suprised as you.

It's been hours, and I'm still trying to figure it out.
I'm a complete novice, please understand.
Question.
When I click the subscribe button, the folder is automatically created, right?
I'm sure it's working as you posted in the video,
but there is no executable file in the SEB folder.
Why is this happening?
Please help me.

@Low Amplitude this is "normal", steam structure is hardcoded in the script. Any other environment will make it fail.

i slowed down the parameter and it works, thank you!

DOG is right.
I'm not relly supporting this mod anymore, although it was still working on the last version of the game.
If you have troubles with "file not found" or can't even start the script then you should first look at the installation process : 100% of those error were due to wrong installation. Try to replicate the steps i've made in the tutorial video.
If scripts works but interrrupts sometimes it is mostly due to computer health. Try to lower the parameter "search process speed" to solve this issue. This will give more time to the script to write and read things.

make sure the "addons" folder is spelt correctly

My game always throws an error "addons/SEB/scripts/seb.se, line 10: File not found: '#/scripts/selecttarget.se'" when exploring and then the SEB window reopened
I have tried to verify the content but steam told me nothing wrong

Followed all the steps opened space engine open the menu I run the program, nothing happens for 10 seconds and then the program open back up

About the Hud not getting back after the script interruption, you're right it's funny how i didn't even realize that before. Well, i probably won't do any more updates, the best i can tell you is that there's a useful shortkey in the game to bring back the Hud (i think it is ² or Ctrl+²).

There are nine levels of octrees in the game : to simplify there are potentially at least 8^^8 "sub-sectors" ,each containing thousands of galaxies.

That means that script will potentially lead you to one galaxie between 1000*(8^^7) procedurals plus the 11 000 real ones ... then you have two more options the limit the randomisation to real galaxies or irregular ones.

I let the statisticians fix my potential mistakes about the counts, but however, it is enough galaxies in my opinion :) .

If you wanted more filters on the galaxies like "Elliptical" or "class Sc" then it will require a complete new devloppement with another tool than Autohotkey, because the game itself doesn't provides those informations through the galaxy name or through the native scripts commands and logs.

About seeing more galaxies, maybe i don't understand what you means by "see more galaxies". The only technicals limits applied to the randomisation for galaxies are :

-make sure the next galaxies visited is in a neighboor octree of the current one , to avoid endless travels. That doesn't means you will stay in the same place.

-make sure the absolute parent octree remains the same (octree 1) to avoid hundred of giga-light-years travels between each tours.

-make sure the galaxies number into the abosulte child octree is between 0 and 1000 (because octrees of the ninth level -usually irregulars galaxies - rarely contains more than 1000 galaxies).

I cannot blame you for the lazyness :), since the script is done for lazy people ^^.

Repeating the same object happened to me once or twice in like... 1500 hours of running. There are already some patches in the code to prevent choosing the same object twice, but it can stil fails whent the scripts have some difficulties to follow the logfiles, which is totally depends on the current health/stress of your computer. You can lower the parameter "search speed" to avoid this.

This is a really good and relaxing addon, but there are issues of course: Issue 1: Repeating the same object. Sometimes it gets stuck on any object, forcing you start the thing again. Issue 2: It doesn't show the GUI once it finished. This is worse than issue 1 because it forces you to restart the application. Extra issues: It's not endless. I put this in the extra issues because there might be an option that allows you to see more galaxies, but I'm too lazy to watch the tutorial. Besides, I was able to set it up without the tutorial. Still a great addon.

Yeah, I realised if you manipulate the timeflow while approaching the surface of a planet and flying close to the surface the camera movement got messed up (flying backwards if time is forwarded).

Okay, so for the moment there is nothing you can do about it and that is totally okay.

Thank you for your answers.

With best regards

Just to add that this 2-3 seconds moment we are talking about is probably the most sensitive part of the scripts, and surely the one who took me the longer to solve.

In fact, if the timeflow were going on, you would see one glitch per error message hidden. the scripts usually tests 2-3 destination before taking you to a new one. each test results in an error message that freezes the game and also breaks scripts ongoing. so you 'll have several little freezes on this moment - similar to glitches.
There's also another reason why the time got stopped at this point. It has come in one of the last updates, i don't remember exactly what for, but i remember that i had to stop it for a good reason. It could probably be for the positionnal onto the orbit before the planet landing.

Hello and thank you for your fast reply.

Is it also the case for the timescale that it has to be stopped until a new destination is found? The camera movement is totally okay for me but the sudden stop of the timeflow realy is a bummer and destroys the immersion a little bit.

Have a great day and keep up the good work.

@KStrike
There are several deep reasons why the script stops at this moment :
-centering/aligning with the new destination would make a glitch if camera was moving.
-Script "tests" new destination and spawn error messages (hidden), which cancel any moves. It has to test the destination, because sometimes it doesn't exits or it is not loaded by the game. And there is no in-game scripts commands specific for this ; so we are forced to play with error message while searching, which directly means that camera must be stopped.

That script is awesome.

May it possible that the timeflow continues and not abruptly stops if one planet/moon etc. observation is finished?

In my opinion it looks weird if moons travel around a planet and suddenly they stop traveling seconds before a new object is approached.

Is there something I can change in the scripts to let the timeflow go on?

With best regards

Absolutely amazing, thank you for this!! would love to see even more options.

great great script thank you

Yes you must not launch the script before entering planetarium mode in SE.

sorry, thinking the script launched SE..... launching SE than running script is ok...

Hello, i've got the same problem than mtndewv, i've seen your video several time to be sure to put the directory SEB in the good place. It is in SpaceEngine/addons, i've got the error: failed attempt to launch program or documet: Action: < startmsg.se> Params: < > Specifically: le fichier spécifié est introuvable line # 1176: RunWait;%SEexe% startmsg.se
Thank you for your help

Many thanks! I must've gotten so excited to use the mod after initially discovering it that I completely missed the paste step. Works as well as I had hoped, thank you for the amazing mod. :)

@mtndewv

You must copy the SEB folder that you'll find in Steam\steamapps\workshop\content\314650\2689038344, you must copy it Into SpaceEngine\addon . Anywhere else will make things fail.
The behaviour you describe clearly shows that the SEB folder is not in the good place.Check the tutorial video again to see where i've put it, no matter if SpaceEngine is installed on C or D.

Despite how much I want to use this mod I cant seem to get it to work :( in the console I just keep getting the errors,
ERROR: File not found "#/scipts/startmsg.se"
ERROR: File not found "#/scipts/galcheck.se"
ERROR: File not found "#/scipts/consoledown.se"
But these files are inside of the scripts folder when I check. I have tried launching the exe from the Steam\steamapps\workshop\content\314650\2689038344 directory and a copy of the SEB file on my desktop but when I try running any of the modes I just get the message "ready!", it opens se, spits those errors in the console then reopens the SEB menu. Not sure that it would make any difference but I keep my steam games in my D: directory rather than C: like mosy people do.
Already running on latest version and on a windows computer.

Alright, thanks for the quick and informative reply! I'll keep those tips in mind whenever i'm playing this awesome mod :)

Hello Kokomi Main. Glad you enjoyed the mod !

1) about orbiting black holes : For supermassive black holes , you must save it as a star system (when you are far from it and it didn't load all the subsystems on screen) so it will stop approaching far enough of it most of the time. But there could be issue with any corpse with a diameter of more than 40 Au.
For small black hole, you must save it as a planet (while you are inside the star system), So it will approach close enough.

2)Observation time is a ratio from 0 to 100 % corresponding from 2s to 30s , not linearly.
minobsplt=2
maxobsplt=30
obsplt := minobsplt+(((observtime**2)/10000)*((maxobsplt)-(minobsplt)))

I hope i have answered to your questions :) .

3) some recommandations :
- increase orbit speed and roll rotation for better sensations. Increase it a lot relatively to the approach speed.
-Best rendering is global speed (travel/approach/surface) around 30 % (in my opinion).

BTW i have some questions:

1) Does the camera go to and orbit around Black Holes? I have the "Insterstellar" ultramassive Black Hole installed, and it'd be hella amazing if the script could pick it as a target and orbit around it.

2) Is the "Observation Time" measured in seconds, minutes or something? It's hard to determine an appropriate viewing time for me without knowing exactly how much time i am setting it to.

Tried this on the Geonosis planet, and i have to say, i love this. How come this doesn't have any rating yet - if i had the power, i'd put this at the front page with 5 shining stars. Thank you so much for the time and effor put into making this, i'm never playing SE again without this mod now S2

Bruh, this is something i've been waiting for ever since i found out about Space Engine in my life. I'm so excited to try this out - i'll post my thoughts later :D

-the hide toolbar option ; already tried, problem is i can't unhide it properly ^^.
-the observation time might be the parameter you are looking for.
-i don't understand your third question.
-this happen because of lags generated by nebula. This create a mess in logs, and SEB cannot interprete them anymore, and so after 5 seconds without interaction with logs, it abandons and shows up menu. Try slowing down the parameter "search process speed", it can help.

*it might be cause the nebula is too far from the galaxy the script starts in.

And sometimes while being in a nebula (only noticed in nebula) the script just randomly stops and shows the gui, no error code given.

Also is there something for the addon to make it wait until the game loads to stop, or is it already implemented?

ąnd maybe a option for a timer until observation (time until you stop to observe)?

You can also add a hide toolbars option.

Because they are old options that suffers from regressions that wasn't spotted yet (despite hours of test). A routine when a program grows a bit too much. However, this time i'll wait a bit more before next update , in case you find other issues.