Don’t worry, I’ll make clearer for launcher 2.0.1 by making that option entirely hidden when it can’t be selected.
Are you playing in GLES2 mode? I don’t get that bug:
The “Force GLES2 rendering mode” is disabled in the launcher
If you computer doesn’t support GLES3 it can still fallback to GLES2. Can you provide the first few lines of your game logs to confirm the graphics card you have and the renderer it picked?
Log
Godot Engine v3.5.stable.mono.thrive.d2ad79a40 - https://godotengine.org
Godot Engine v3.5.stable.mono.thrive.d2ad79a40 - https://godotengine.org
Godot Engine v3.5.stable.mono.thrive.d2ad79a40 - https://godotengine.org
OpenGL ES 3.0 Renderer: Mesa Intel(R) HD Graphics 500 (APL 2)
Async. shader compilation: OFF
Mono: Log file is: '/home/gcastro/.var/app/com.revolutionarygamesstudio.ThriveLauncher/data/Thrive/mono/mono_logs/2022-12-03_12.42.53_77.log'
This is Thrive version: 0.6.0.0-rc1 (see below for exact build info)
Unhandled exception logger attached
Startup C# locale is: pt-BR Godot locale is: pt_BR
user:// directory is: /home/gcastro/.var/app/com.revolutionarygamesstudio.ThriveLauncher/data/Thrive
Game logs are written to: /home/gcastro/.var/app/com.revolutionarygamesstudio.ThriveLauncher/data/Thrive/logs latest log is 'log.txt'
Failed to open settings configuration file, file is missing or unreadable. Using default settings instead.
Doing delayed apply for some settings
Set audio output device to: Default
Set C# locale to: pt-BR Godot locale is: pt_BR
No SteamClient class found, not initializing Steam
SimulationParameters are good
This version of Thrive was built at Saturday, 03 December 2022 09:46:27 from commit 9f508dfde02abd66411319256b59aa80bbef107d on branch master
We were opened through the Thrive Launcher
Thrive Launcher started us, launcher hidden: False
Loading mod Nodes into the scene tree
Jukebox now playing from: Menu
Jukebox: starting track: res://assets/sounds/main-menu-theme-1.ogg position: 0
Startup successful, removing startup info file
Okay so it does use GLES3, but you seem to have a bit of a dated intel graphics, so it could be a driver bug. But could you provide step by step instructions how you go from launching Thrive to seeing the issue? So we can see if anyone else can reproduce the bug.
My first impressions:
Stability:
No crashes or bugs in general found so far, nice work!
Launcher:
- I appreciate the extra effort put into automatically porting over settings from the old launcher, nice job! It may just be me, but it seems a bit faster in starting up than the old one?
Fossilisation:
- Everything mentioned about it seems to work.
- Nice function, as a side effect also lets me check out what organelles a cell has without having too stand next to it and zoom in.
Not quite sure why most of the icons are faded while some are solid here:
Night-and-day:
Played at default 180 setting.
- I think it adds nicely to the challenge of playing as a photosynthetic organism. Mainly in that you have to make sure to store up enough glucose so you can survive through the night. This was a little extra thing to keep in mind without being too punishing.
- The default day length setting seems pretty natural, I don’t really get an initial feeling that it should be longer or shorter than now.
- The visual effect of the change in lighting is just… nice to look at? It adds something to the life of the game.
- I love the buttons at the top of the editor to switch between different times of day for processes. Having it change the actual lighting is an especially nice touch.
- Is auto evo running on the new average daytime glucose production? It definitely seems to not like my basic chloroplast build now.
Auto-evo:
Are AI species like this supposed to show up so early? Seems like a lot of mutations right away. Was the standard AI mutation rate increased? It’s at 2 on Normal now. Seems like this actually allows AI to evolve much faster than the player.
1 Like
That at least was my hope that it is faster. Especially in seamless mode the goal is that the C# runtime starts so fast that it is basically unnoticeable delay before Thrive is started. That’s the benefit of not having to start up a full chromium browser to run JavaScript in it.
Faded icons show what you have already fossilized so that it is easier to notice what are new species.
Yeah, it uses the average light values plus a storage score based on how much store the species has.
I don’t remember the mutation rate being adjusted recently, though I may have forgotten some change or another possibility is that with auto-evo changes it encourages species to get mutations earlier.
1 Like
I don’t think the mutation rate has actually been changed, it’s just that the evolutionary tree makes the status of AI species much more visible. I remember I noticed this too back in the Thriveopedia branch.
1 Like
Well, from what I can tell I’d say you were successful then!
Makes sense, and useful.
Then I would say you made the right call in not setting the night cycle as default yet before somebody can take another look at the balancing.
That was my second thought. This is one of the main reasons I was looking forward to having the tree in-game actually. So right now we’ve got things like:
I’m pretty sure you can’t actually keep up with that as a player. Whether that is desirable or not is a design choice, of course. I’ll probably look into the effects of this more myself another time.
i found a (probably)minor bug with this
it says 1183.5/11 ATP
i think it has to do with the absurdly high storage stat based on the fact that it only started doing that once i got to that storage amount and that the stored ATP is the same as my storage stat
This is the second time I see this being reported so I’ve opened an issue:
Oh and this was problem even in earlier versions of Thrive.
I can’t wait to play Thrive again once my PC gets fixed
me try to strest testing that stuff:
I now almost move in 5 FFS already (testing photosyntsing in the new day-night cycle, I make it works, to much)
I even try to low the grafict and the properment, that only help alitle (in the pic its not even the full grow)
edit:
its now down to 1 FFS and its still not finish:
btw, its my new laptop in 16 ram
1 Like
Thrive definitely needs some optimizations.
Turning the entity limit to tiny is the only thing that reduces late game lag. Also in case you hang around in a patch too long the duplications of you just stay around forever (even over the entity limit), which needs some kind of fix (and is nothing new in this release):
2 Likes
yes, its was alreay in FFS in the lower entity limit, but to move to other patch its a great idea also that I did not try, but u know, i not the type of moving to other patch that i am the king there.
also - something weird i did see in the auto-evo: idk if its a feater or something else, but i see comper to me (there player) they see to be haveing more MP and more organelle. after the evolution tree have been added, i just see what i have been evole and what they have evolve and see the mismatch in there.
maybe it me or its what use to be, but it seen a bit unfair.
need more testing
Okay my first impresions
Starting up the game it does seem faster. The new intro is nice very detailed and fits with the rest of the game.
Now onto the bugs i have managed to find.
First off i have noticed that when changing the membrane some of the textures seem to have a clipping? issue
most that is the most noticeable with the Cellulose membrane and others.
Here is a small list of the membrane types that seem to have this issue (unless this is intented then i apologize).
- Cellulose
- Silica
- Calcium Carbonate
- Chitin
The remaining two membrane types dont have this issue.
Fluidity / Rigidity does not seem to affect this.
Thats everything that i have found for now. I will keep you updated.
1 Like
Apparently, the snaky trail of unlimited glucose still happens.
(Reproduce after maxing out glucose storage, then hit the guaranteed glucose cloud)
Not very high priority I would say.
1 Like
0.6.0 is out now so further feedback should go here: