This site makes extensive use of JavaScript.
Please enable JavaScript in your browser.
Live
PTR
10.2.7
PTR
10.2.6
Beta
[Isolated] Dressing Room / Profiler: models not loading
Post Reply
Return to board index
Post by
3acpaheu
Hi team,
I'm getting 500 error from zamimg.com. It is not the first time I've experiencing issues with zamimg. From time to time is not working or working very-very-very slow thus affecting not only modelviewer but the whole site experience.
For example, modelviewer request the following png file:
http://wow.zamimg.com/modelviewer/textures/161858.png
and server response code is 500.
It was working fine several hours ago. Hope you will find solution for this issue soon.
WBR,
Ilya.
Post by
VitaDoden
I used to have the issue where the character is a gradient of colors (rainbow model basically) but now everything seems to be just whitewashed with a bit of particle effects on the set I'm trying to view.
This is the link to what I was trying to look at:
Stormrider's Vestments (Normal Recolor)
#modelviewer:22+0
Asume this:
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Refused to execute script from '
http://adadvisor.net/adscores/g.js?sid=9276253823'
because its MIME type ('image/gif') is not executable.
256stormriders-garb#modelviewer:22+0:1 GL ERROR :GL_INVALID_OPERATION : glDrawElements: attempt to access out of range vertices in attribute 0
stormriders-garb#modelviewer:22+0:1 WebGL: too many errors, no more errors will be reported to the console for this context.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
is what you wanted from the developer console.
Post by
adutzu89
Model viewer is never working as intended, the issues started for sometimes now (I think after wow legion data was starting to get added), the issues are randomly placed, what I've seen is that for periods of time, same part of the models are not getting loaded or textured fully(white model). I tried latest Chrome/Firefox/Opera with latest flash players on 3 different OSes (Ubuntu and Windows 7 & 10).
The most issues appear when trying to load epic gear, and newer gear, another thing to note: in dressing room when the selection of items appear in the pop-up, those that which do not have any thumbnail loaded are 100% chance to not load.
From what I can figure out is that the server download is cut-of before the client can finish the download....or server-side not sending the proper files.
Hope my feedback helped.
Post by
Archanos
Mine are all white body place holder & the items do not even apear
Post by
perculia
Yeah model tweaks continue on the Alpha, as helms are still disabled.
Post by
culicidae
Hi,
the Dressing room for Legion does not load on Firefox due to about 20 same origin policy violations.
e.g.:
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at
http://wow.zamimg.com/modelviewer/meta/character/nightelffemale.json
. (Reason: CORS header 'Access-Control-Allow-Origin' missing).
I've tried clearing the cache and similar actions to no avail.
Cheers,
culicidae
Browser: Firefox Nightly, 47.0a1, 2016-03-06
OS: Windows 10 Professional English, Eval Build 14279.rs1_release.160229-1700
Post by
Frag971
Only shows white models and the page is still freezing for a coupel of seconds on load.
Was searching, found this, dunno if it's relevant
http://stackoverflow.com/questions/27560812/google-font-not-working-giving-an-error-no-access-control-allow-origin-header
Post by
Animosa
I have the same problem in Firefox, modelviewer only shows shoulder and hair, the other parts are blank white.
Post by
3acpaheu
Well, going to this link seems to return the picture as expected (some kind of belt?) Is it giving you a 500 error when
you
try to access it directly?
Hi Ammako,
this link is one of resources failed to load. I have issues with Dressing room from time to time. Not always. The problem is that wow.zamimg.com returns 500 instead of requested file. But it is intermittent issue. Maybe there was some kind of maintenance work on servers\loadbalancer. It will be great if in future maintenance work will not affect server stability. I suspect that servers are redundant thus dressgin room should work.
Post by
markapalooza
Why does model viewer/dressing room have to be based off the Alpha anyway?
Surely it would be better to have it be based off live rather than have several things go broken for months because Blizzard is tweaking things during Alpha. Or is it not possible to have it be based off Live?
For Legion-specific equipment and models, yeah, but I mean, for everything else, they don't need Legion models.
Is it something like, it can only be based either off Alpha, or off Live? (if it's based off Alpha, then a lot of things are broken for a while because Blizz is tweaking stuff for Alpha, but if we base it off Live, then it becomes impossible to view models for any Legion stuff.)
Great point Ammako,
We originally had two separate model databases and viewers.
www.wowhead.com
would point to the legacy modelviewer and legion.wowhead.com would point to the new one.
This was working well for awhile, but as time grew on became increasingly harder to support since it was two different data sets AND two separate modelviewers.
Also when perc would link things in news posts, a lot of models wouldn't show up because it was on the wrong subdomain.
To put it short, it just created a whole lot of problems and even more frustrated users.
To everyone having missing textures,
we believe this is due to the heavy load on our current servers.
We have a plan to move everything on a new reliable server next week.
We cannot guarantee that this will fix the majority of modelviewer problems, but that is our hope.
Blizzard has settled down with fundamental database changes, so we are able to get you the latest models even quicker.
Again, we appreciate everyone's patience during this unstable time.
Thank you,
Mark(##RESPBREAK##)2##DELIM##markapalooza##DELIM##
Post by
skystorm382
Noticed the robe and foot issue yesterday as well. All robes are now pants.
Post by
markapalooza
Noticed the robe and foot issue yesterday as well. All robes are now pants.
Should be fixed now.
Post by
markapalooza
I won't argue that yeah, that may have caused a lot of problems, and frustrated users, but this is causing a lot of problems and frustrated users too. We do have you guys responding to us about certain problems sometimes, but a lot of the time, it feels like I report problems and it falls on deaf ears.
I wouldn't mind all the issues, if they were being acknowledged and if we were being given an answer as to what is causing the issue.
Several things have been reported as broken and we still have no idea why they are broken. Could someone at least tell us if the problems are on Wowhead's model viewer's end or if they are due to Blizzard changes?
Because if it's due to Wowhead having an issue, then it could be looked at and fixed, and if it's because of Blizzard changes in Legion alpha, then I'll just patiently wait until Blizz fixes it on their end. No big deal to me, honestly; what annoys me is that too many things sometimes get really broken and we are left in the dark as to what causes it.
A lot of chest pieces are simply not showing up in Outfits model viewers, but that may just be a problem with the Outfits feature, because if you view them in Dressing room or on their respective item pages, they show up as expected.
Cloaks seem to not show up at all anymore either, no matter which model viewer I view them in. Is this due to Blizzard messing with capes, or does Wowhead have trouble rendering capes right now?
Furthermore, there's the issue where every robe I find seems to not really be a robe at all anymore, and the robe bottoms part has transformed into pants. Could that be related with the heavy load problem you just mentioned that gives missing textures? It started happening today. It seems to load textures and apply them onto the character model, but ignores the shape of the models, if that makes sense.
(Likely also related to the issue where gloves and boots no longer have "3D" models that stick out, and are now all just skins applied onto your character's skin.
Example
because I'm terrible at explaining.)
I don't mind if problems are occurring because of changes in Legion Alpha, I just want any problems that may be on Wowhead's side to be fixed if possible. I'm not saying that everything I just pointed out was Wowhead problems (well, the missing chest pieces in Outfits likely is), but I would appreciate if someone could take a look at it and let us know if those problems are caused by Legion Alpha, or if something is actually broken with the model viewer that could be fixed.
I want Wowhead's model viewer to be good, so I want to report problems when they arise, but I would like to receive some feedback about it so that I at least know what's going on. I don't mind having to wait weeks or months for Blizzard to fix things on their end, if the problem is a Blizzard problem, because at least I know that a fix is coming eventually.
Will someone let us know when the server move will be complete? I want to go back and check everything again after the server move to see if it fixed most of the problems.
The pants/skirt problem should be fixed now.
We attempted the migration to the new static server last night, but it was not successful.
The team will try again next week.
We have noticed some weird shoulder armor issues.
This is definitely Blizzard.(##RESPBREAK##)2##DELIM##markapalooza##DELIM##
Post by
perculia
We are getting Legion alpha builds every week, and as we've stated before, they cause a lot of instability. We do not have assistance from Blizzard as to what data has changed, so every week we test the viewer, determine if there are bugs, and if these bugs are something on our end or Blizzard's. This is on top of the usual updates for news and general updates to get the new models on the Dressing Room, npc, item pages etc. A lot of this takes some time to sort out, so we don't have more frequent updates to give (although, Mark has replied 20 times in the last month here which is prety awesome imo).
We have also given some updates on the static server issue, including a really long detailed post by Erorus, and we had some server maintenance this week to try to fix it.
This also ties into an issue of how to more effectively communicate. I think Mark has done a great job, but others prefer communication be even more frequent. There have also been duplicate threads made about the same topic, or replies that have gotten buried. The team discussed this today and we thought a Wowhead Discord would be useful so we could give a casual quick update to a user directly. We should have more to share on this next week, when we do another Site Update post.(##RESPBREAK##)2##DELIM##perculia##DELIM##
Post by
WeWillPawnYa
Pictures or item/model viewer, neither works for me for some time now. Using chrome Version 49.0.2623.87 m which is the latest atm, deleted cache and cookies, etc.
bloodthirsty-wyrmhide-shoulders#modelviewer:1 Font from origin '
http://wow.zamimg.com'
has been blocked from loading by Cross-Origin Resource Sharing policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin '
http://www.wowhead.com'
is therefore not allowed access.
http://wow.zamimg.com/uploads/screenshots/small/247414.jpg
Failed to load resource: the server responded with a status of 500 (Internal Server Error)
http://wow.zamimg.com/modelviewer/meta/armor/3/81373.json
Failed to load resource: the server responded with a status of 500 (Internal Server Error)
bloodthirsty-wyrmhide-shoulders:1 XMLHttpRequest cannot load
http://wow.zamimg.com/modelviewer/meta/armor/3/81373.json
. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin '
http://www.wowhead.com'
is therefore not allowed access. The response had HTTP status code 500.
Post by
Mzp1994
I still have problems with my wowhead and i've had it for the last month. Item models aren't loading and i can't check anything in dressing room or 3D...
This is how it looks
http://prntscr.com/af7enk
Sorry i know this is an old post...
Post by
f4ri
I'm having the same problem and it's been going on for well over a month now so it's not just you.
Post by
Miloscub
Yep having the same problem as Mzp1994 here,every model is just white,no matter what gear is on,what animation is playing or what model it is,hopefully it gets fixed soon! thanks for all your hard work wowhead team <3
Edit: screenshot of the error =
http://puu.sh/nNk3F/ebbbf81901.jpg
Post by
markapalooza
Hey All,
Sorry to hear that some of you are experiencing some texture related troubles.
We are working very hard to address these problems.
Here's how you can help.
1. Provide the link to the model you are having trouble with.
2. Screenshot the errors that show up in the Chrome Developer's Console. (Ctrl + Shift + i)
3. Give the model a couple minutes.
- Sometimes getting the texture can be extremely slow. It could take 5+ minutes to load in rare cases.
- You can find out if it's an error or loading slow by looking at the Chrome Developer's Network tab. (Ctrl + Shift + i, then click Network)
- Here you can see the status of the textures (.png files)....if it says 'pending' it's still on its way.
- A status of 200 means it loaded that texture just fine. If it says 404 or something else, then there was an error.
To address server issues (status 500 errors), we are very close in transferring Wowhead data to a more reliable server.
I will update this thread once we are successful.
Again, thank you for your patience.
Mark(##RESPBREAK##)2##DELIM##markapalooza##DELIM##
Post by
zAce
Loading the texture png's seems to work for me, but it don't seem to load textures.js file (it's completetly empty).
Here's an image:
http://i.imgur.com/O8jU1g8.png
The following error happened when I pressed the "Remove current gear" button:
Uncaught TypeError: Cannot read property 'renderer' of null
Post Reply
You are not logged in. Please
log in
to post a reply or
register
if you don't already have an account.