• Check out the results of the Techtree Contest #19!
  • Listen to a special audio message from Bill Roper to the Hive Workshop community (Bill is a former Vice President of Blizzard Entertainment, Producer, Designer, Musician, Voice Actor) 🔗Click here to hear his message!
  • Read Evilhog's interview with Gregory Alper, the original composer of the music for WarCraft: Orcs & Humans 🔗Click here to read the full interview.
  • Create a void inspired texture for Warcraft 3 and enter Hive's 34th Texturing Contest: Void! Click here to enter!
  • The Hive's 22nd Icon Contest: Creep Abilities is now concluded, time to vote for your favourite set of icons! Click here to vote!

Broken default models when previewing custom skins

Level 54
Joined
Jun 2, 2008
Messages
855
when previewing skins that use custom human arthas texture (such as this, this and this), "arthas_portrait.mdx" and "arthaswithsword_portrait.mdx" appear broken and lacking camera
"jaina_portrait.mdx" is broken in the same way, geometry all over the place and no camera
could it be that it's pulling some broken model from the models repository instead of default one?
arthas.webp
 
Last edited:
broken "herodemonhunter.mdx", it just won't load at all, but _portrait works
same with "illidanevil.mdx", it freezes on a frame from a model you were viewing previously but loads list of available animations
same with "lavaspawnmissile.mdx", "lordofflamemissile.mdx", "infernal.mdx", "infernalbirth.mdx"
 
Last edited:
betaviewer doesn't show anything for me at all, whether it's in skins or models section, "navigator.gpu.requestAdapter returned null."
Try upgrading your browser to the latest version.

You must use a WebGPU capable browser. Chrome, FireFox, Safari and Edge all support WebGPU in its latest version.
 
Last edited:
Try upgrading your browser to the latest version.

You must use a WebGPU capable browser. Chrome, FireFox, Safari and Edge all support WebGPU in its latest version.
i'm on latest version of brave
i found a "Force Enable WebGPU interop" in brave://flags and turned it on, no use

turned on both "Unsafe WebGPU Support" and "WebGPU Developer Features" and it "works": all 4 cores at 90%, i'll stick to old viewer
 
i'm on latest version of brave
i found a "Force Enable WebGPU interop" in brave://flags and turned it on, no use

turned on both "Unsafe WebGPU Support" and "WebGPU Developer Features" and it "works": all 4 cores at 90%, i'll stick to old viewer
all cores at 90%? Sounds like it has no hardware acceleration and it's using lavapipe or some software rasterizer. If you do brave://gpu it will show you if WebGPU has hardware acceleration.

In general, it may better that you just give a shot to Chrome instead.
 
Back
Top