Fedor @fedor@mastodon.gamedev.place

I don't know the future. I didn't come here to tell you how this is going to end. I came here to tell you how it's going to begin.

Llatest GIF from the FishFight. Posted it on a birdsite already, but I really like it and believe it deserves being posted twice :)

I wrote a thing for Patreon! https://www.patreon.com/posts/57523082

Reflection on the future of macroquad and what is going to happen in the next version.

It is paywalled - I am not sure if I want to make it really public :)

Unpaywalled source(don't post it out of mastodon pls): https://hackmd.io/SZJ_TG56RV2m8kwdapG4cQ?view

well, now if I let gmail tab open for some time it just jumps from a usable version to unusable by itself :/

URL from the history made it, but, yeah, thanks google, good reminder to move away from gmail

oh, did gmail just turned off a legacy(usable) version?

I just opened my gmail account and got a giant JS monster :/

https://www.reddit.com/r/gamedev/comments/51564p/comment/d79npmx/?utm_source=share&utm_medium=web2x&context=3

What you must learn is that these rules are no different than rules of a computer system. Some of them can be bent, others can be broken.

Litany Against Despair:

To improve the use of proprietary systems is a misguided goal. Our aim, rather, is to eliminate them. We include support for some proprietary systems in GNU Emacs in the hope that running Emacs on them will give users a taste of freedom and thus lead them to free themselves.

(from https://www.gnu.org/software/emacs/download.html)

In case one wants to cross-compile to msvc-windows, but do not feel like downloading ~15gb of data (and than struggling of getting headers from .exe):

Half of the windows headers live here: https://github.com/icestudent/vc-19-changes

Another half in /extracted from this(absolutely amazing) repo: https://github.com/est31/msvc-wine-rust

Managed to get a nice x86_64-pc-windows-msvc binary from some rust, some c++, and some closed-source .lib/.dll

Commiting rust crimes: https://gist.github.com/not-fl3/ba67e22ba7554f1850e25aaf3f3c07e8#file-past2-rs-L112

I would really like to be able to use coroutines while still being able to time-travel for a little

One of the situations when it is probably impossible, but there is still hope!

(discussion thread: https://github.com/not-fl3/macroquad/issues/296)

Oh, I love this crate's API:

https://docs.rs/stunclient/0.3.0/stunclient/index.html

Clean, nice, explain what is STUN in literally one line.

https://github.com/PSteinhaus/good-web-game a thing I made few years ago to run Zemeroth on web, found a new home!

After Zemeroth moved to macroquad, "gwg" was abandoned and was only collecting dust.
But now ggez people got interested in it!

It's a first of my projects that got some life way after I stopped working on it :)

Updated my gamepad's gist based on this new knowledge:

https://gist.github.com/not-fl3/2125b08f90d6e298bc94d48bcbf19d32

And, yeah, it works! The button on the bottom is always A, button on the right is always B, on both of my gamepads!

Some gamepads, however, do respect the evdev specification.

For example, "8bit do" gamepad has its buttons labeled (A/B/X/Y is printed on the controller).

And 8bit do send correct BTN_A/BTN_B evdev codes.

But because other gamepad do not send correct codes - no one cares, codes are ignored, and after SDL mappings B is A and A is B :/

But this mapping is not
evdev code -> nice name

Its an "index of a button in the evdev bitmask" -> nice name

Soo button code from evdev is just ignored by the majority of games

TIL that linux have a nice header file with evdev joystick button codes: https://github.com/torvalds/linux/blob/master/include/uapi/linux/input-event-codes.h#L379

And you can tell that, say, BTN_A is pressed just from a raw evdev event.

BUT some gamepads do not care and just give random numbers as buttons codes in their events.

And there is a mapping file everyone uses https://github.com/gabomdq/SDL_GameControllerDB/blob/master/gamecontrollerdb.txt

that maps gamepad button to correct codes

I don't know the future. I didn't come here to tell you how this is going to end. I came here to tell you how it's going to begin.

In 20-30 years Unity may become a new Oracle - a giant corporation with lots of money, outdated tech, sitting on all those patents for basically anything in the game engine, suing everyone around

https://www.patentguru.com/assignee/unity-ipr-aps

from the same birdsite thread:
https://twitter.com/xeleh/status/1435199526407708674

I never cared about software patents, living in a nice open-source bubble where everything seemed nice, open, and possible, with imagination as the only limit

But this hits close to home:
https://pdfpiw.uspto.gov/.piw?PageNum=0&docid=10599560&IDKey=53ECD0571430

Apparently, Unity can sue most of Rust engines for patent violation now :/ and if(when) we will be big enough - we will need to care about patents doing our open source

Depressing!
I guess it was like this all the time and I just did not noticed

(source: https://twitter.com/xeleh/status/1435136911295799298)