Yes. Pedantically (as if this is a real language to begin with) it would be “Trick AND NOT Treat”.

Do I understand it right that it’s a free replacement of the still copyrighted game assists such as textures and models, and not the code itself? I’m curios if the level design wouldn’t also fall into this.

Huh. I did as well. Like /use/bin was for user installed applications and such. You learn something everyday.

Yeah the issue is I wouldn’t want to compromise quality too much. But I might just start saving up now for whatever valve is cooking up next :) Another issue with using a quest is that you have to run the occulus app (when wired), eating up some of that sweet precious VRAM.

I got a Quest 3 that I use with a USB-c cable. Price is great but having to fiddle around with video compression settings on top of all other VR settings has proven to be a bit tedious. I’m still trying to figure out what pcvr headset to go for that won’t complete drain my bank account (there’s probably tons of used ones out there).

Glad to hear VR is possible and getting better on Linux though!

Oh what’s your Linux setup for VR? I thought it was very janky still? Once I get my storage server set up I was planing on moving fully to windows except for a small drive for VR titlea.

And then you realise your dumb endless ls-ing has pushed the command off the history list

Last time I checked codium out it couldn’t support the vs code marketplace/plugin repo. Is this still the case? I should take another look at it either way though :)

Edit: I answered my own question by reading some more comments. So looks like there are alternative plugin registries. I’ll definitely have a go at switching now.

Just to add my two pennies (that’s a saying, right?), I do use VS code as my default text editor. Professionally and for other projects in C++/C# I use the full fat visual studio. But for scripting, config editing, hex files, todo lists and such I use Code.

I’ve never been much of a person who needs to shave off every possible second in my workflow with macros and plugins, my brain is just not fast enough to out pace my hands, and the command palette does pretty much all I could wish for.

I of course wish it was fully open source, but for being the only Microsoft product I daily it isn’t too bad.

You will still have private/public sections, interfaces (unless you class them as inheritance), classes and instances, the SOLID principles, composition over inheritance. OOP is a lot more than just large family trees of inheritance, a way of thinking that’s been moved away from for a long time.

I’ve only used DaVinci for small projects, so I don’t know their eco system too well, but what made you buy a product when you were having problems getting it to work? :O Does the studio version offer better hardware acceleration or something like that?

It was a lot of fun for me. I did it without a virtual machine (would not generally recommend) on a older laptop I wasn’t using anyway. I wasn’t very successful in the end however. My own built kernel couldn’t produce any vga output. I tried to fix it for a handful of nights, but in the end gave up and called it good enough :P So I might comeback to it later to fully complete an installation.

But it was good learning oppertunity. It showed that just compiling a version of the Linux kernel isn’t very complicated. It even comes with a very nice TUI to select your build options!

And then plug those values into a image generation service to give users a visually intuitive way to see if there’s cooffe or not!

Should really start practicing dependency injection, so you can create any kind of gameplay you want easily!