• 0 Posts
  • 685 Comments
Joined 2 years ago
cake
Cake day: November 7th, 2023

help-circle






  • vram in the context of an igpu like an apple chip or strix halo is the same thing as system ram. its shared memory

    its why strix halo and apple m4 chips are popular with users running local ai models, because those will cost you 2-4000$ for 128 gb ram, while the closest nvidia alternative is the RTX 6000 blackwell with 96gb vram costing 2-4x more.





  • the main thing you get back is a better cpu governor to manage power consumption on 2d games. Reviews like the Phawks points out that microsoft kinda handed it off to the handheld makers to optimize for battery life. So in the instances such as getting 8hours of battery life running dead cells because the system doesnt really need to push that much to run the game, the Windows handheld is stuck on a higher performance clock and has a significantly shorter battery life time.

    This would be extremely visible if more lighter games are tested, which typically aren’t for reviews like this because its not really fun to show a bunch of games all hitting 60 if you cap framerate.


  • the wine part, its more or less based on the end goal of the software. traditional game emulation is software that is used to try to mimic the hardware in question. Wine focuses on trying to be windows, rather than the physical PC hardware itself, so the type of thing youre trying to emulate is fundamentally different.

    emulation in general is functionally a compatibility layer. Wine exists on the highest level of compatibility layer because its not trying to rewrite what the hardware is necessary doing (as both the hardware is the same)

    Wine is the same level as Teknoparrot is (teknoparrot is compatibility layer for arcade maches that use X86 based pcs for hardware), vs MAME, which emulates non x86 based arcade machines.

    it gets mega pendantic because of how closely emulation and compatibility layers are intertwined, but they arent two overlapping circles. a compatibility can use emulation but doesn’t require it.

    I just like defining the difference between the two simply by the goal. emulation targets machine to then get to software, where compatibility layers target the software directly. and will target hardware only when necessary.



  • Dudewitbow@lemmy.ziptoGames@lemmy.worldMy AYN Thor
    link
    fedilink
    English
    arrow-up
    6
    ·
    21 days ago

    the bigger wall with switch emulation on android is that mobile companies are terrible at writing gpu drivers when compared to conventional desktop/laptop graphics vendors. its why for example the older snapdragon gen 2/3 outperform their newer snapdragon elite counterparts in emulation.

    theres significantly more setup time on mobile because some of the jank doesnt “just work”







  • thats why theres always an ongoing debate on grading homework. what matters more are the exam grades to show if a given person understands a concept, but it runs the riak of more people failing out without the weight of graded homework easing up scores.

    back in middleschool, i was basically told i would instantly fail a geometry class if i didnt start doing homework, despite aceing exams. The goal of homework is to teach students more about meeting deadlines, and that message often gets lost in education.