- Edited
Audiobellum
0 means OK (no error).
The error codes are listed here:
https://docs.godotengine.org/en/stable/classes/class_%40globalscope.html#enumerations
Scroll down to enum Error.
Audiobellum
0 means OK (no error).
The error codes are listed here:
https://docs.godotengine.org/en/stable/classes/class_%40globalscope.html#enumerations
Scroll down to enum Error.
Does anyone know any alternative ways of reloading a scene?
It might be due to Autoloads. Those are always present and outside the normal tree.
One more iteration of my low poly character. I've been watching Sherlock Holmes cartoons and that's about the level of detail I want in my characters. Still low poly. I can get a lot of variety by morphing a base mesh and changing clothes, colors, etc.
fire7side Nice, I've been up to something very similar though with a lot more shader code and watercolor paints than polygons. It's a shame I'm away from home for a week. A week with no photo scanner or sketching backlight. In theory based off the pages of incomprehensible handwriting and scribbling in the one sketchbook i have, it should work fine once I have the backlight making sure i'm drawing the same lines 50x over for the photo scanner.
I just made an app in Godot that generates lottery numbers. Current jackpot is $1 billion dollars. You gotta be in it to win it!!!
fire7side Take a week and study this. The longer you struggle, the longer you wind up remembering what you learned.
The hardest part is translating the 4 words gdshader and glsl disagree on, such as COLOR is actually gl_FragColor in glsl. I won't say how long that took me to figure out as a wee 21 year old, otherwise I will be embarrassed, and maybe even shed a tear.
cybereality
Are you going to market the app? What's sad is that there would be people who would buy it.
cybereality Yeah, autoload was a part of the problem. I also discovered that using export var for the array of weapon numbers I had was a bad idea. Thanks for the help.
DaveTheCoder Are you going to market the app? What's sad is that there would be people who would buy it.
I'm going to try to win first. Then I'll sell it for like $99 and say it has some secret algorithm. Step 3. profit.
Check out this robo I found at OSU while staying with a friend in town.
Photo's not mine, my camera's too old and this laptop's SD card slot too small.
Edit for background info, the college of engineering in my state is really cool. Campus owns a fleet of these little guys for delivering campus food to students. I tried it once, their voice isn't as cute as they look and the cookie was too sweet.
I wasn't there for the photo I just showed, I got mine just today when i went to the ATM on campus and found one who got confused by 30 students and jammed another 2 robos at a sidewalk intersection. They figured it out surprisingly fast, less than a minute was enough for all 3 to reorient and get unstuck. It might have been less than 10 seconds if I didn't try to take a photo of the pumpkin one while it was stuck just in time for them to decide to move and kick me in the shin.
I got the photo later while it was waiting in line to cross the road.
Going back 4 months to when we talked about JPEG XL...
cybereality Support is still not ready (as I said, it's barely final) but there is a GIMP plugin and Chrome just added support
and Chrome has already deprecated JPEG XL and will remove its code.
Their reasons:
https://www.phoronix.com/news/Chrome-Dropping-JPEG-XL-Reasons
Obvious corporate Mafia Tactics, since Google has a competing format (that is not as good).
They can't compete fairly, so they use Mafia Tactics. Same as Apple really (with OpenGL and Vulkan).
Like when Google purposely delivered 360P resolution video on YouTube to Firefox users for 2 weeks, when there was no technical reason (faking the user agent fixed it).
https://bugzilla.mozilla.org/show_bug.cgi?id=1233970#c25
Or in 2020 when YouTube forced VP9 support for higher than 1080P video, even though H264 works fine, effectively making everything except Chrome choppy on YouTube.
https://support.mozilla.org/en-US/kb/firefox-4k-ultra-high-definition-youtube-videos
I rarely use google at all, be it search engine, browser, OS or whatever. It simply has no benefit and I don't have to grow any gray hair. Actually, I have also stopped growing hair :-)
Shave-and-a-hair cut ...
Firefox neither supports JPEG XL.
And there is this:
https://jpegxl.io/articles/rans/
https://www.theregister.com/2021/03/13/microsoft_ans_patent/
Already 1.5 years old. What became of it ?
I stay with png for now.
cybereality
Yeah, kind of makes me want to use it more.
Back in 2000 a company I worked at was bought out by Unisys.
Unisys was the company that had acquired the patents on the compression algorithm in the GIF file format. When they realised what they owned (they got it as part of another company buyout), they were the ones who started charging something like $3000 for a license to put GIFs on a web page, and some fee to add GIF load/save to software. They are the reason a lot of software back then dropped GIF support (or had it as a plugin instead of integrated) and why the PNG format was invented as a competitor.
I resigned. I was rather angry about the GIF thing at the time. Plus the managers were assholes (the director blamed me for changes made in the software 6 months before I joined the company. Idiot). Oh, and burn out from bad project management. But definitely the GIF thing was an influence.
I think JPEG XL can stand on it's own merits, even with Google's apparent sabotage. The format is good, vastly better than JPEG/PNG/GIF and similar to WebP (beats it in some areas and I think overall better in feature set).
And honestly, how long has WebP been out, even with Google backing, and it's barely supported anywhere. So I don't think they are a good judge of standards.
JPEG is just ancient technology, it was made when people were using 14.4 K modems. We shouldn't still be using it. PNG is a solid format, but GIF could not be worse.
And every other new format has been destroyed by either patent encumbrance or these stupid corporate format wars (which always end up with everyone losing).
I think JPEG XL still has a shot, and if the open source community adopts it and it gets better support, Google will eventually add it back in.
And, to be honest, it's not finished. So it is technically experimental, last time I tried the SDK it didn't even compile. So it could still happen.