Virtual Desktop is the only app which makes Quest 3 usable for work. And it is bad thing because it is available only on Win and Mac. Unfortunately, Linux alternatives' video encoding/postprocessing is inferior. Judging by my WiVRn experience. Hopefully that changes
Interesting observation. This is what was lurking in the back of my mind when I was playing Path of Exile. But I usually thought it would be very elegant to implement it in the form of Lisp macros that transform all the computations into fast code that would need to be executed every tick.
I also think something similar could be implemented for an in-game rig of animated characters. In order to cut off the computation of animations that don't affect the result in any way at an earlier stage — for example, when the character switches weapons. This could make animation code more CPU cache friendly as many conditions could be optimized out.
I’m not generating code for this, at least not currently. It’s more like lowering authored content into fixed-size runtime data that the hot path can consume.
The animation graph example feels like the same general shape.
Stat recalculations are pretty much immediate, yes. The only thing that takes a while is calculating the nodes with the most potential gains, since you're in effect calculating reachability, combined stat increases, etc, which is a few thousands to millions of calculations depending on how far you look.
FPS drops in PoE would not be caused by damage recalc: this is done entirely server side and on application of the damage/dot tick. That drop you're seeing is just loading the assets and recompiling some shaders, if anything.
But also: it doesn't need to be realtime. Your damage is a simple math formula, applied against another for enemy defense, for each hit instance. There are definitely some builds that stress servers due to the sheer amount of hits/tick, but that's a matter of optimisation. PoE lowers server ticks when it can't follow.
The post is talking about optimizing for build damage/resistance/etc, crafting a build. Which probably doesn't even take into account conversion shenanigans, over time things like wardloop that requires setup, cwdt and a load of other things. This is not an optimizable thing in any reasonable time, and human application of logic is pretty much faster.
Small clarification: I don’t mean optimizing buildcraft in the Path of Building sense, as in searching the space of possible gear/tree/support setups and finding the best upgrade.
I mean the engine-side representation problem after the player already has a concrete setup.
The output is not “the optimal build.” The output is things like increased damage, more multipliers, pierce count, area radius delta, conversion rules, status payloads, etc.
I agree that global build optimization quickly becomes a much harder and more human-guided problem. I’m mostly interested in how to keep normal runtime resolution from becoming a giant matrix of skill/support/item/status branches.
A decision to move native because of the crisis seems like an expensive populist move to please not very solvent users. Why bother with that if many predict the RAM crisis will last merely until 2027?
Supply of RAM isn't really limited by natural resources - silicon is literally one of the most abundant materials on the planet. It's limited by the construction of billion dollar factories.
How does it replace Obsidian though? I somehow think the author does not fully understand that knowledge management systems are inherently interactive and need to handle queries like in databases because they are databases.
1) Are there any benefits in replacing a personal private project git repo with jj? I usually just commit straight to master in order to just not to lose the changes and be able to roll back.
2) Are there any pros in doing so in a project with many large binary files (3d models, images)?
You can switch an existing git repo to jj by using:
jj git init --git-repo my-repo
I think (but CANNOT PROMISE) that just removing the .jj folder will bring you back, but definitely take a backup of .git before you try this in case I’m wrong.
No that is correct when in colocate mode (which is the default mode). Simply removing the .jj folder will "de-jj" the repo entirely, but will leave you in a headless state. Simple to fix with a `git switch` though.
If you are _not_ in colocate mode, the .git folder is located _inside_ the .jj folder. So worth checking!
Godot is nowhere near to something like C# HPC, Jobs and Burst. And I’m afraid even GDExtension can’t help with that.
At least not with Godot’s scene structure which prioritises simplicity over performance.
reply