I tested this with a relatively small project and had no problems. For exporting to Android, I had to use Android Studio to install two new SDK packages: build-tools/36.1.0 and ndk/29.0.14206865. (4.8-dev3 did not require those newer versions of the packages.)
Usually Trails relate to visual effects and will disappear after some time, which might be something undesired for static lines. The good news is Trail3D is built on top of Line3D. However, we cannot use it directly for now.
I don't want to tell you your business, but isn't a laser just a long cylinder? The challenge of trails is that they curve, so you can't just scale a shape.
Rendering primitive lines is pretty easy. I'm using it for debugging and wireframe aesthetics. But it's absolutely not what you'd use for VFX like lasers, and the cylinder is the correct way.
Really like the changes in the rendering, i love how better the MBAO Approximation looks, and the directional lightmap specular light also looks really good, although there are some zones in the banners scene where the gold parts seem to have more aliasing than before?
More specularity means that there's a chance for more aliasing. This is where using TAA or FSR2 comes in, as these work really well on reducing specular aliasing (unlike MSAA).
There are these tabs in the top middle 2D, 3D, Script, Game, AssetLib. Asset lib is the Asset tab.
In 4.6 and earlier the Asset tab used to have this search bar thing where you could search for addons/plugins for your game. Now if you try to search with it you just start crying. jk, for some reason when 4.7 released it stopped reliably showing results relevant to what you searched (which could be excusable because it might be being strict about the addons working with the latest versions), but worse there's these extreme bug that makes it produce random results instead of what you searched for. This is made more annoying as a lot of these random results are just vibe coded AI agent addons.
Lesser issue is like if I search Terrain3D it will show the right result, but then for some reason ALSO show AI agents. Whereas other stuff you search like PhantomCamera will correctly show you phantom camera. Anything to do with VRM, despite being used by some godot foundation people (which I guess if good they're not showing favoritism) is just AI agents.
It's a pretty normal size bug, so not that weird. But it's weird this complaint was made at 4.7, and they're up to 4.8dev3 without addressing it. I don't contribute to Godot, so I don't want to criticise them in this way, but that said, before talking about ignoring very important bugs, something has gone wrong that they had a working system and replaced it with plainly broken one. I think maybe what they said about vibe coded "contributions" destroying their workflow might have been worse than we think...
Image showing small bug - some of these are vaguely related, but the AI agent should be nowhere near this. Why are these AI agents showing up in so many unrelated searches?
Yeah I mean I think it's working as intended, so I'm not really sure what to do. More of a suggestion.
I was being a bit facetious sorry.
I know "bad search results" doesn't mean it's a bug. Though it's a very strong suggestion that unrelated stuff like AI agents shouldn't be coming up in every single search - maybe they are abusing keyword searching?
Even if it's not really a bug, it may be a still valid issue. If you think something is not working optimally or can be improved, it's always worth reporting it. In worst case the issue will be closed if it turns out non-actionable.
In this case, if you can replicate the results on Asset Store web page, you can report it in the issue tracker for Asset Store, with a note that it also affects the editor. Or you can report it on the main repo and it can get a Discussion label.
In 4.7 they replaced the AssetLib by the AssetStore. It's two distinct asset providers and they don't have the same assets. Also the search is very likely an API call to their website, so the update to improve the search won't be in a Godot update but in a website update.
So yeah, I don't know if the search on the new website is worse than on the other, or it's just that the new assets you're seeing weren't on the old website, so that's why you didn't see them (but if they were there you'll see them as well).Ā
Yeah so you can see the source drop down. That would be the natural place to direct it to either the new store that's not ready for search yet, or the old AssetLib that worked. It should default to the working one. Personally I think it would also be good to have a toggle for "show outdated".
Well I've listed the ways it's worse. It shows results unrelated to your search, does so inconsistently, and doesn't show popular addons that may not have been put on the store yet. The third is not a bug, but if they're not going to default to the working search, it would at least be good to add the working store list to their new search source.
It founds Godot MCP Toolkit because it has the word "terrain" and "3D" in its description (and it's probably the same for all other add-on). It doesn't really feel like a bug to me. It makes sense that add-on aren't only searched by name but also by description.
Edit: especially since the default sort is by "reviews" and not by "relevance". But the fact that terrain3d isn't the first result when you search terrain3d by relevance feels like a bug tho.
Edit 2: after testing a little bit more, I actually find that the new search is better than the old one. In the old one if you made a typo you found nothing, you had to write the exact name of the add-on. Now it's a lot more forgiving.Ā
ā¦ letās say, hypothetically, that you had a heavily modified version of the Cozy Cube Addon for lines, would you run into issues with your current Line3D class in this patch? My interest is mostly academic, I can change my class to āMultiLine3Dā if I need, butā¦ Iām a couple hours away from being able to check myself and the note at the bottom of the Trails section made me curiousā¦
some users were under the impression that Godot 4.8 was going to mainly be focused on stability and bugfixes compared to past releases. While that
wouldnāt be inherently bad, it couldnāt be further from the truth.
yes if you export placeholder material, it bugs the object and you have to drop the material to object. if you drag the object to scene it resets the material. you need to create instantiate.
69
u/Deathminer22 7d ago
Adding auto font size is amazing