search

Anarchyg / lolmodelviewer

Automatically exported from code.google.com/p/lolmodelviewer
0 stars 0 forks source link

Viewing issuge(black shadows) #2

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
Hello :)

What is the expected output? What do you see instead?
  I see black shadows all over models (attached screenshot shows it)

What version of the product are you using? On what operating system?
  Windows 7 64bit 
  program - 1.11 lolviewer
  GPU - AMD 5750HD with newest drivers
  Netframework 4.0

Questions
  Why its happening ? my card is broken or its just a bug ?

thx in advance

Original issue reported on code.google.com by pnbgraph...@gmail.com on 26 Oct 2011 at 12:18

Attachments:

GoogleCodeExporter commented 8 years ago 
I've never seen that bug before.  I have an nVidia card and Poppy looks fine. 
(I just tested it with the latest patch.)  I'm not a GPU programming expert so 
I'm not really sure what could go wrong in the code between the different card 
manufacturers.  

It's possible their is bug in the code that only manifests itself on AMD cards 
or maybe there's a problem with your set up.  There's no way I can really tell.

However, thanks for checking out the program and submitting a bug log.  Sorry 
I'm not much help with solving your problem. :(

Do all the models look like that?

Original comment by Sapphire...@gmail.com on 26 Oct 2011 at 3:56

GoogleCodeExporter commented 8 years ago 
yes, all models looks like that :C

Original comment by pnbgraph...@gmail.com on 26 Oct 2011 at 6:55

GoogleCodeExporter commented 8 years ago 
maybe some of ur friends know anything about openCL/AMD GPUs issues ? I was 
looking everywhere and couldn't find any answer to resolve this ;C

Original comment by pnbgraph...@gmail.com on 12 Nov 2011 at 9:29

GoogleCodeExporter commented 8 years ago 
+1 Me too! but after building the application myself, this problem was fixed. I 
think it's just a glitch or something.

Original comment by blmar...@gmail.com on 28 Nov 2011 at 12:34

GoogleCodeExporter commented 8 years ago 
could you send me fixed version  ?xD

Original comment by pnbgraph...@gmail.com on 28 Nov 2011 at 5:08

GoogleCodeExporter commented 8 years ago 
Hey guys.  Thanks for the feedback and sticking it out with this bug.  Since 
multiple people are experiencing the same thing, it's most likely a problem in 
the code.  I'll look into it and see if I can find something.

Original comment by Sapphire...@gmail.com on 30 Nov 2011 at 1:14

GoogleCodeExporter commented 8 years ago 
Hi,

I am just wondering if there is any progress on solving the issue with black 
shadows as I also have this problem.

Thanks!

Original comment by elcaptit...@gmail.com on 11 Dec 2011 at 4:28

GoogleCodeExporter commented 8 years ago 
Hey Elcap,

Are you running an AMD card as well?

In other news, I've reproduced the bug on my machine by changing some of the 
shader code.  What you're seeing is only portions of the model being lit by 
specular lighting.  Parts of the model where the specular component is zero, 
render as black.

Now, this is kind of interesting.  If the other lighting components, ambient 
and diffuse, were actually broken, you wouldn't see correctly textured and lit 
portions of the model at all.  Poppy would basically look entirely black with 
some white highlights in some areas; no texture information anywhere.

So, I think AMD's GLSL compiler is over optimizing the lighting model.  If 
there's no specular component, it just bails and renders black which is not 
intended.  All three components should always be considered regardless of the 
results any of the other two.

Anyways, I have some possible solutions.  However, I can't test them on my 
machine since I have nVidia hardware.  If someone wants to test them, email me 
and I'll send you some tweaked versions of the program.

Original comment by Sapphire...@gmail.com on 13 Dec 2011 at 1:26

GoogleCodeExporter commented 8 years ago 
Hi Saphire,

Yes, I do have an AMD card and am happy to test any new versions which may 
solve this issue. I have sent you an e-mail.

Thanks a lot!

Original comment by elcaptit...@gmail.com on 13 Dec 2011 at 4:19

GoogleCodeExporter commented 8 years ago 
Hi guys,

I made some changes to address this problem.  Elcaptitain tested them and they 
seem to solve the problem.

I'm going to mark this issue as solved.  If the problem returns, just open a 
new issue about it in the future.

The fixed version of the code will be released in version 1.14 which I will be 
releasing shortly.

Original comment by Sapphire...@gmail.com on 13 Dec 2011 at 11:31

GoogleCodeExporter commented 8 years ago 
The change for this is integrated into 1.14.

Original comment by Sapphire...@gmail.com on 14 Dec 2011 at 12:17

GoogleCodeExporter commented 8 years ago 
it works ! thx :*

Original comment by pnbgraph...@gmail.com on 14 Dec 2011 at 5:34