I always liked the viewmodel shadow Halo 4 had, was sad when Halo 5 removed it.

dont ever buy no centered viewmodel mod from the gas station bro

I think the average gamer is more likely to notice the shadows looking funky on the viewmodel instead of no shadows at all. You can literally see the shadow of the playermodel Assault Rifle on the viewmodel of the assault rifle, and it bobbing at a completely different cycle to the viewmodel bob.

If you want a somewhat decent way to make a shadow appear on the viewmodel, like making it where the player's body would accurately block light from hitting the gun, you could attach a mesh to the viewmodel that sits behind the camera that serves as a shadow caster. Not sure if that'd translate to Halo 4 at all, it works in doom 3

I'd rather it look flat and weird rather than have this distracting shadow that doesn't align with the camera position and viewmodel movement animations. It's pretty distracting once you notice the discrepancy

Halo 4 mods are neat but enabling that thing where you can see the thirdperson shadow on the viewmodel is so distracting. Even more so because the walkcycle for the viewmodel doesn't line up with the playermodel walkcycle, so you can tell it's misaligned

Benelli M4 Viewmodel anims by Altron! I set up a whole pipeline for unreal-standard IK rigs with vertex bone controls being workable as roblox-compatible FK rigs, which has worked great You can still see the navmesh/cover visualizer as well here lol #robloxdev #roblox

Mistake 1: Business logic inside your widgets. Your widget calls the API, transforms the data, AND renders the UI. It feels productive. It's a trap. Widgets should only render. Put logic in a ViewModel or Controller. Always.

ViewModelってなんでUMGデザイナータブで動作確認できるようにしなかったんだろ　謎

zenn.dev/solenoid/articles/b… ViewModelがどうやって構成変更を生き延びているのかとか、最近追加されたComposable関数スコープのViewModelを作るためのAPIについてその責務と仕組みについて解説する記事を書きました

knockout.JS is the real king everything you see around now is just a successor idk i feel it’s exact honest representation of what the data flow look like it’s deterministic as hell you can’t escape waterfalls dooming even in the OG knockout.JS idk what if it had a build time compiler step to just generate the static dependency graph in the original Knockout, the runtime has to find the dependencies by watching the stack in your version, compiler would scan the data-bind expressions and the ViewModel, generating an Execution Plan before the code ever runs Knockout is notoriously bad at handling async tasks. compiled knockout would use Reactivity-as-a-Pipeline $binding(Price) .map(v => v * Tax) .pipe(v => v.toFixed(2)) .toDOM("#price-display"); compiler takes that pipeline and turns it into a hardcoded path so there is no function wrapper , no observable observer simply just :) price changes Value goes to the map function , goes to toFixed , Value touches the DOM knockout should have win :(

prerendered viewmodel doohickey This will not be a real game

Bro please, why do players use this viewmodel 💀

Future versions of the OS and applications will need an additional UI layer — something like a ViewModel-Agent-Interface (VMAI). The goal is to avoid wasting resources on OCR by retrieving the current view's state as native structured data instead.

Funny, I just posted earlier how I prefer the material on the Plasma Pistol from the 2025 build The iridescent blue-purple color shift is more easily visible in first person in that version, at least from the angle seen in this specific comparison That said a lot of iridescent effects are seen in the current build on the Banshee, Ghost, Hunters, Elites, the Plasma Rifle etc from specific angles, so I'm sure the Plasma Pistol has it too still from the right ones, I just hope it's visible in the first person viewmodel

We're a little slow on posting right, there's a lot of work being done that isn't as exciting as cool physics or a new gun. Settings menu is being filled out. Viewmodel offsets are in!

algum jogo de fundo(ou ia ) overlay do viewmodel e hud do mine