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!
Just because it'll be the same format doesn't mean that it'll have the same support. I'm sure there will be new ribbons/effects which will surely crash WC3. You'll probably be able to import WC3 models into SC2 though.
--donut3.5--
All sc2 models contain much more complex functions than simple wc3 models, ranging from different texture maps, IK bones (completely new animation system) and such. I am 99% sure it will not be mdx. Sc2 isnt based on the wc3 engine, its a completely new one.
All sc2 models contain much more complex functions than simple wc3 models, ranging from different texture maps, IK bones (completely new animation system) and such. I am 99% sure it will not be mdx. Sc2 isnt based on the wc3 engine, its a completely new one.
All sc2 models contain much more complex functions than simple wc3 models, ranging from different texture maps, IK bones (completely new animation system) and such. I am 99% sure it will not be mdx. Sc2 isnt based on the wc3 engine, its a completely new one.
Well, .mdx is just a way of compressing text into a format readable by a Blizzard .dll. TDR mentioned that they tend to use .mdx in all of their recent games, so I don't see why not. I'm not sure if this means they'll be compatible, I know for sure SC2 models in WC3 will not be, but vice versa *may* work.
--donut3.5--
According to blizzard interviews, while the extension might still be .mdx, SC2 models won't be compatible with WC3 models, in any way, including importing wc3 models into starcraft 2.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.