Thinking about Old CSGO Viewmodels... I will never forgive what they did to the m9 . It is that deep

Injects screenshot capture into iOS app process. DEBUG-gated: accesses ViewModels, SwiftData, ImageRenderer. ios-marketing-capture skips XCUITest — simctl locales step coordinator.

I'm really not sure why OW is one of the only FPS/TPS games I know that doesn't have a flipped viewmodels feature. CS has it, Valorant has it, TF2 *especially* has it, so seeing OW still not have it even a decade later after launch is genuinely baffling to me. I wonder why?

Since I've been on a huge Overwatch playing-spree lately, I noticed the absence of a specific feature. So I wanted to make a post simply showing my appreciation for said feature in the games where it DOES exist. Left-handed viewmodels. Thank you for acknowledging my existence.

.@ESLCS can you make it so i don’t have to see players viewmodels anymore i genuinely despise some of the players viewmodels

lowkey one of the worst viewmodels in the game 🤫

Will there be customizable weapon viewmodels?

I am still digesting what we've gotten in this massive update: 1) All the new pet galleries (I absolutely love them, btw) do not support Scene Graph, even though the Static Meshes are exposed. Wasn't SG the target logic for it? 2) Weapon templates are cool, hopefully we can get more variety from the game soon, so we have some options to play with. Fundamentals are great, but content is missing. Also, custom weapons block the camera and have no SFX for faraway shots. 3) The pet template doesn't have any functionality built into it; it's only visual. Would love to see what we can do with pets, but there is no example atm. 4) The persona device was overhauled without any documentation or communication. Heard there is a way to make it work still, but a little weird. 5) Scene graph material instances broke? Haven't seen people mention it, and it seems like a big issue. 6) Monitor performance and new memory metrics feel not useful without knowing what the verse or scene graph is doing; these two usually take the most memory and cause the "stop point" in all maps. 7) Live edit load times still feel long to me, even on a new project with basic stuff built into it. Something about "initializing validation checks" (why do I care as a creator if this has to load, feels useless for a simple live edit session) 8) Even though URC mentioned speed fixes for various things like naming/duplicating, it's still as slow as it was when it regressed a year ago. To compare, duplicate any material on UEFN and UE5, and notice the difference in how long it takes. 9) New gizmo broke the combinational gizmo; to fix, enable the legacy gizmo in editor prefs. I haven't fully given it a go yet, but I will soon, so I can't comment on it. In general, I absolutely love the massive update we've gotten and its content. Still, I wish we had a little more focus on improving the overall editor experience rather than jumping into new shiny things all the time. What I want to see: - Core UEFN missing functionality patched - really basic things like controlling the player, camera transitions, overlapping cutscenes to work, player instigation on cutscenes given correctly or through choice, audio in general - Features for memory optimization: Verse device memory breakdown, Scene graph memory breakdown, counting memory per data layer, and showing memory as an outliner column, combine all memory menus/UI into one cohesive stat that is always updating without user feedback (and show everything affected). - Editor experience: polish naming/duplicating assets, don't prevent renaming, fix directors with a user popup prompt, auto-fix wrong naming rather than give error, remove dirty asset edits and useless popup clutter from the editor, explain better how data layers work to the user (and visualize them as well). Reduce clicks in viewbinding / verse field workflows. - Large features: Ability to add more levels to a project, or unload logic to give back memory, render widgets in space that DONT face the player, add index on verse fields, ability to use verse fields and viewmodels together, live edit to sync with landscape edits and UMG, Audio volumes effects, Post process/particles in screen space, connect FN assets with SG, visualize connections from verse and SG to other actors in scene, control player's skin with head/torso settings (for helmets), their animations and facial animations. Additive animation curves to work, UMG tinting to work on all things, not just fonts.

SwiftData ResultsObserver: an equivalent to NSFetchedResultsController to use SwiftData in... ViewModels? 🤔

So ResultsObserver is like @.Query but for ViewModels? Like an NSFetchedResultsController.

does anybody have any good custom viewmodels. big ones. i got a nice paint on my shotgun but i can only see like 30% of it in the viewmodel and that bugs me

🔄 Spin heads with custom crafts and inspects from viewmodels to charms to aspect ratios 🔄

Claude Cood calls Swift viewmodels "VMs" and I get confused for a second every time, no matter how many times it happens

Is there a limit to how much jiggle one can put their viewmodels through? I think not #gamedev #unrealengine #indiedev

Then you also have those incredibly ugly animation mods or something really stupid like left handed or centered viewmodels

Shipped a solo “how far can I get?” FPS/survival tower. WebGPU Three.js, FP viewmodels, editor, NPCs, weapons, planting, missions SpacetimeDB. 100 FPS in tight furnished units (up to ~500k tris). The pain is culling across 20 floors / 456 units. Open source. Play with it if you want.

📷 Supersconto  per EVENTO 29 Giugno a Milano Compresi 2 workshop  sullo sviluppo con ecosistema Gemini (di Peter Friese & Marina Coelho ) e sui ViewModels (di Arnaud Giuliani).📷 Guarda l'agenda aiheroes.it/agenda ALL DAY a 99€ ­ticket.synesthesia.it/synest…

Now you will be able to scope viewmodels to specific components as well instead of screens. Checkout the post here to know more about the new compose changes for this. #JetpackCompose #Android saurabharora.dev/posts/per-i…

Screen level ViewModels work well but they can quickly get bloated with mixed logics completely unrelated to each other. Compose released some new APIs for this. Read more in this post by @iSaurabhArora 💯 saurabharora.dev/posts/per-i…

This might sound counter intuitive to you if you’ve been doing Android for the last decade, but makes sense 👇 ViewModels should desirable be scoped to the specific part of the UI that they are relevant to. That is normally not a complete screen, but something smaller.