[QUOTE=Piett;29321848]Since it's a Valve issue, were gonna have to wait on their time. I'm not sure if even Valve has taken notice of this bug.[/QUOTE]Did you read my last post? It's not a Valve issue; at least, not the error I'm having. This is just GMod.
I'm glad Garry has taken notice of this, but I should point out again that it's probably not phong. It's likely that it's the "Clamp S" and "Clamp T" conflicting with something that was updated in GMod - maybe related to the new effect that appears when you create ragdolls?
Also, although bit off-topic,
[QUOTE=npx190;29309466]Its just considering the graphical thing effected others not the same way, it is extra frustrating with the engine thing, especially when the next Mythos Comic is delayed from publishing[/QUOTE]"Especially"? Aww, thanks! <3 I appreciate the thought. :)
[QUOTE=Mythos;29323036]Did you read my last post? It's not a Valve issue; at least, not the error I'm having. This is just GMod.
I'm glad Garry has taken notice of this, but I should point out again that it's probably not phong. It's likely that it's the "Clamp S" and "Clamp T" conflicting with something that was updated in GMod - maybe related to the new effect that appears when you create ragdolls?
Also, although bit off-topic,
"Especially"? Aww, thanks! <3 I appreciate the thought. :)[/QUOTE]
Actually no, apparently DoD:S is having the same issue. Problem might not be localized to Garrysmod. Or, somehow, Garry broke DoD:S. Probably the former.
Hold your horses guys. ValvE isn't that big of a company and they just started shipping Portal 2. It'll take the a while to fix the engine. Also, any news on Portal 2 content on GMOD?
[QUOTE=DesumThePanda;29329285]Hold your horses guys. ValvE isn't that big of a company and they just started shipping Portal 2. It'll take the a while to fix the engine. Also, any news on Portal 2 content on GMOD?[/QUOTE]
Check garry's twitter. He said he has come across many many issues so that is bad news, however he then quoted Justin Bieber "Never say never". So that means he will keep trying.
IMO i would rather him work on bug fixes initially, THEN adding new content.
I will try to contribute to the solving of these issues. I will have pictures or videos up by the end of the week (assuming photobucket solves its hardware issue). The more information garry has, the better.
[QUOTE=fury_161;29327998]Actually no, apparently DoD:S is having the same issue. Problem might not be localized to Garrysmod. Or, somehow, Garry broke DoD:S. Probably the former.[/QUOTE]If it's the issue shown in this thread, it's not the same issue. But let me see screenshots of the DoD:S bug, please.
I'm thinking I'll make a hex of Alyx with fixed textures and see if it works.
[B]UPDATE[/B]: A little after-the-fact, but I removed phong from Alyx's model just to be sure that was really the issue. Turns out the whole Clamp S/Clamp T theory was completely off-base.
[img]http://img593.imageshack.us/img593/1610/gmflatgrass0203.jpg[/img]
That's Alyx with the phong removed and Eli with phong, just as comparison. So, yes, it really is phong doing the weird black crap.
Sorry I can't really be much help here, guys. If you want, I can upload the phong-less Alyx materials to GarrysMod.org as a temporary fix.
Same shit is happening to me, It only started happening today, after I updated all the source games.
I finally figured out the Source SDK faceposer, I made a scene for kleiner so I could do a greenscreen test... Now I am waiting for this to be fixed, it makes GMod unplayable in my case, it's just really frustrating...
Since Valve knows how valuable Garrysmod is to steam, Garry most likely has Valve on speed dial. He has acknowledged his issue. So [b]if[/b] it is indeed a source engine error, he will most likely contacted Valve about it and are working on a fix (hopefully).
And I just noticed that I am also getting TF2 blood effects. (Didn't notice it at first.)
I am just checking garrysmod.com every so often to see if there is an update.
[QUOTE=Stormexdante;29407714]Since Valve knows how valuable Garrysmod is to steam, Garry most likely has Valve on speed dial. He has acknowledged his issue. So if it is indeed a source engine error, he will most likely contacted Valve about it and are working on a fix (hopefully).
And I just noticed that I am also getting TF2 blood effects. (Didn't notice it at first.)
I am just checking garrysmod.com every so often to see if there is an update.[/QUOTE]
I have a feeling that Valve are more focused on Portal 2 at the moment, it could be a while before this is fixed. The issue only started recently, for me anyway.
People keep saying it's an engine issue just because Garry posted that hypothesis, but you're jumping the gun. It might be, yes, but I, for one, only have this issue on Garry's Mod - even Half-Life 2 works as it should.
I might be wrong, but, if it were an engine bug, it'd be generalized. And no, that DoD:S issue is not exactly the same thing, people. But I'll wait and see. I'll tell you one thing, though: it's getting a bit frustrating. I can't get anything done in GMod and my free time is nearing its end. I know Garry's busy and probably trying to figure this out or at least telling Valve about it, but I still hope he figures it out soon. I have faith in him.
Well Mythos, I don't know what you got going on, since you made a quick fix, worse case scenario, I guess you could try faking the faces for your comic?
[URL=http://img816.imageshack.us/i/mythosalnpxmixed.jpg/][IMG]http://img816.imageshack.us/img816/1580/mythosalnpxmixed.jpg[/IMG][/URL]
damn it this looked better further away :(
I never photoshopped a comic together, but I bet you know how to work out the technical details of that.
I don't know if it is a source engine issue or just restricted to garrysmod. Either way, in the eyes of an average consumer, they don't really care. most average consumers don't care where a bug is coming from, they just want it fixed.
For me I am not in urgent need of this getting fixed so I honestly can wait but most people can't and those are the average consumers. They don't give a crap where the bug is from, they just don't want the bug.
I am not an ignorant consumer. I actually check updates, read the news node and I understand that things just take time. I got a little off topic :p
Now as long as we know that Garry is looking into it, we just got to wait.
[QUOTE=Mythos;29411550]People keep saying it's an engine issue just because Garry posted that hypothesis, but you're jumping the gun. It might be, yes, but I, for one, only have this issue on Garry's Mod - even Half-Life 2 works as it should.
I might be wrong, but, if it were an engine bug, it'd be generalized. And no, that DoD:S issue is not exactly the same thing, people. But I'll wait and see. I'll tell you one thing, though: it's getting a bit frustrating. I can't get anything done in GMod and my free time is nearing its end. I know Garry's busy and probably trying to figure this out or at least telling Valve about it, but I still hope he figures it out soon. I have faith in him.[/QUOTE]
I really hope you're right, I was making a Faceposer SDK greenscreen comic to play in Gmod. I was gonna submit it to machinima if it was any good. About it only being Gmod, it happens in DoD:S for me, the same face and helmet black patch that happens. To be honest I think it's got something to do with the EP2 engine, my reasoning is because it is only EP2 characters and it's version of the HL2 character that messes up.
[editline]25th April 2011[/editline]
[QUOTE=Stormexdante;29416325]I don't know if it is a source engine issue or just restricted to garrysmod. Either way, in the eyes of an average consumer, they don't really care. most average consumers don't care where a bug is coming from, they just want it fixed.
For me I am not in urgent need of this getting fixed so I honestly can wait but most people can't and those are the average consumers. They don't give a crap where the bug is from, they just don't want the bug.
I am not an ignorant consumer. I actually check updates, read the news node and I understand that things just take time. I got a little off topic :p
Now as long as we know that Garry is looking into it, we just got to wait.[/QUOTE]
I would hardly call wanting it fixed "ignorant" because I have a deadline to ship my FPSDK Gmod movie, I have been following Garry's Blog, Garrysmod.com and the news feed. Thinking that everyone else ignorant IS being ignorant.
I just really hope they fix it soon! Peace :)
[QUOTE=Stormexdante;29416325]I am not an ignorant consumer.[/QUOTE]Nobody called you ignorant. Please don't get me wrong.
[QUOTE=Dragon Master]About it only being Gmod, it happens in DoD:S for me, the same face and helmet black patch that happens.[/QUOTE]Alright then, if it's the same black shadow all over, then yes, it must be an engine error. Though, admittedly, I wasn't aware that DoD:S had been updated to the 2007 engine.
[QUOTE=Mythos;29425224]Nobody called you ignorant. Please don't get me wrong.
Alright then, if it's the same black shadow all over, then yes, it must be an engine error. Though, admittedly, I wasn't aware that DoD:S had been updated to the 2007 engine.[/QUOTE]
Basically it happened once I had updated my games in steam :( I hope it gets fixed.
Ok for those of you who don't already know here are a couple of fixes for the phong problem, they both worked in my case anyway so hopefully they will for you too.
1) Enter r_worldlights 0, this disables any phong sources so the phong won't show up. It does cause some other lighting minor lighting issues but mostly unnoticable.
2) I have found, with the help of mastachief19, that only materials using phong with a phong exponent texture are affected by this bug so if you comment out the [code]"$phongexponenttexture" "texturehere"[/code] line in the .vmt and replace it with [code]"$phongexponent" "50"[/code] it will fix the problem. The only downside is that the whole material now has the same phong exponent level but I think it still looks better than no phong at all. You can replace 50 with any value you like between 0 and 255.
It worked really well on my vehicle models.
[URL="http://img94.imageshack.us/i/2011042700005.jpg/"][IMG]http://img94.imageshack.us/img94/4171/2011042700005.th.jpg[/IMG][/URL][URL="http://img577.imageshack.us/i/2011042700004v.jpg/"][IMG]http://img577.imageshack.us/img577/8176/2011042700004v.th.jpg[/IMG][/URL][URL="http://img27.imageshack.us/i/2011042700003.jpg/"][IMG]http://img27.imageshack.us/img27/8516/2011042700003.th.jpg[/IMG][/URL][URL="http://img845.imageshack.us/i/2011042700002.jpg/"][IMG]http://img845.imageshack.us/img845/7285/2011042700002.th.jpg[/IMG][/URL][URL="http://img846.imageshack.us/i/2011042700001.jpg/"][IMG]http://img846.imageshack.us/img846/4590/2011042700001.th.jpg[/IMG][/URL]
Well, that's good for a temporary fix, I guess, though it's still not good enough for screenshots and comic/machinima making. Thanks, Master Chris!
[QUOTE=Master Chris;29475535]Ok for those of you who don't already know here are a couple of fixes for the phong problem, they both worked in my case anyway so hopefully they will for you too.
1) Enter r_worldlights 0, this disables any phong sources so the phong won't show up. It does cause some other lighting minor lighting issues but mostly unnoticable.
2) I have found, with the help of mastachief19, that only materials using phong with a phong exponent texture are affected by this bug so if you comment out the [code]"$phongexponenttexture" "texturehere"[/code] line in the .vmt and replace it with [code]"$phongexponent" "50"[/code] it will fix the problem. The only downside is that the whole material now has the same phong exponent level but I think it still looks better than no phong at all. You can replace 50 with any value you like between 0 and 255.
It worked really well on my vehicle models.
[URL="http://img94.imageshack.us/i/2011042700005.jpg/"][img_thumb]http://img94.imageshack.us/img94/4171/2011042700005.th.jpg[/img_thumb][/URL][URL="http://img577.imageshack.us/i/2011042700004v.jpg/"][img_thumb]http://img577.imageshack.us/img577/8176/2011042700004v.th.jpg[/img_thumb][/URL][URL="http://img27.imageshack.us/i/2011042700003.jpg/"][img_thumb]http://img27.imageshack.us/img27/8516/2011042700003.th.jpg[/img_thumb][/URL][URL="http://img845.imageshack.us/i/2011042700002.jpg/"][img_thumb]http://img845.imageshack.us/img845/7285/2011042700002.th.jpg[/img_thumb][/URL][URL="http://img846.imageshack.us/i/2011042700001.jpg/"][img_thumb]http://img846.imageshack.us/img846/4590/2011042700001.th.jpg[/img_thumb][/URL][/QUOTE]
Thanks m8, Those cars of yours look sexy as hell. I hope that fix works I kinda have a Faceposer thingy.
Cant find an answer anywhere else.....but has there been any recent news about this getting fixed?
Ive been working towards a big model pack release and I want to know if I need to go back and change my VMT values or just assume it will be fixed.
I think the best way to make Valve more aware about this would be to make screenshots of the bug in TF2 (needs to have HWM enabled mind you) and use its Bug Report feature to send them so they directly get it
[QUOTE=Davebrown;29778948]Cant find an answer anywhere else.....but has there been any recent news about this getting fixed?[/QUOTE]Not that I'm aware of, sadly.
This issue effects Gmod, DOD:S, HL2DM, TF2 (doesn't happen as bad as in other games, only when you get blown up and see your gibs and your gibs show this issue). R-Worldlights 0 solves it in these games.
The weird part about DOD:S is when you do set it it does fix the issue until you shine your flashlight on someone and then only that person shows like you didn't set that console command.
I have been at it with valve support, they are blaming it on faulty/failing video hardware. i am trying to get them to see otherwise but its like trying to punch through a brick wall.
I would suggest that people seeing this issue start a Valve support ticket. If enough people complain to valve about this issue the more of a chance they will finally see this issue as a Source engine issue that needs to be fixed.
[QUOTE=madmax2069;29979871]This issue effects Gmod, DOD:S, HL2DM, TF2 (doesn't happen as bad as in other games, only when you get blown up and see your gibs and your gibs show this issue). R-Worldlights 0 solves it in these games.
The weird part about DOD:S is when you do set it it does fix the issue until you shine your flashlight on someone and then only that person shows like you didn't set that console command.
I have been at it with valve support, they are blaming it on faulty/failing video hardware. i am trying to get them to see otherwise but its like trying to punch through a brick wall.
I would suggest that people seeing this issue start a Valve support ticket. If enough people complain to valve about this issue the more of a chance they will finally see this issue as a Source engine issue that needs to be fixed.[/QUOTE]
The general scheme of things is if a bug doesn't affect their biggest titles in a major/gameplay experience reducing way then they simply cannot be bothered to fix it. I remember at the turn of the 2010 engine update last year, there was a shadow bug where dynamic shadows cast onto props from a flash light would bug out and look odd. They said they were going to fix it. It's still not sorted.
The only exception to this is something security related. Anyone active in gmod over the last year or two will know what I'm talking about.
[QUOTE=Master Chris;29475535]Ok for those of you who don't already know here are a couple of fixes for the phong problem, they both worked in my case anyway so hopefully they will for you too.
1) Enter r_worldlights 0, this disables any phong sources so the phong won't show up. It does cause some other lighting minor lighting issues but mostly unnoticable.
2) I have found, with the help of mastachief19, that only materials using phong with a phong exponent texture are affected by this bug so if you comment out the [code]"$phongexponenttexture" "texturehere"[/code] line in the .vmt and replace it with [code]"$phongexponent" "50"[/code] it will fix the problem. The only downside is that the whole material now has the same phong exponent level but I think it still looks better than no phong at all. You can replace 50 with any value you like between 0 and 255.
It worked really well on my vehicle models.
[URL="http://img94.imageshack.us/i/2011042700005.jpg/"][IMG]http://img94.imageshack.us/img94/4171/2011042700005.th.jpg[/IMG][/URL][URL="http://img577.imageshack.us/i/2011042700004v.jpg/"][IMG]http://img577.imageshack.us/img577/8176/2011042700004v.th.jpg[/IMG][/URL][URL="http://img27.imageshack.us/i/2011042700003.jpg/"][IMG]http://img27.imageshack.us/img27/8516/2011042700003.th.jpg[/IMG][/URL][URL="http://img845.imageshack.us/i/2011042700002.jpg/"][IMG]http://img845.imageshack.us/img845/7285/2011042700002.th.jpg[/IMG][/URL][URL="http://img846.imageshack.us/i/2011042700001.jpg/"][IMG]http://img846.imageshack.us/img846/4590/2011042700001.th.jpg[/IMG][/URL][/QUOTE]
wait, what do i open it with? notepad? i'm a model/material noob.
[QUOTE=mralexs;30024425]wait, what do i open it with? notepad? i'm a model/material noob.[/QUOTE]
Well hopefully you won't have to anymore, apparently valve have tracked down the cause of the issue and it should be updated fairly soon: [url]http://www.youtube.com/watch?v=Ii1tyVeIePY[/url]
[QUOTE=Master Chris;30024442]Well hopefully you won't have to anymore, apparently valve have tracked down the cause of the issue and it should be updated fairly soon: [url]http://www.youtube.com/watch?v=Ii1tyVeIePY[/url][/QUOTE]
I'll believe it when I see it. Though the music in that youtube just brought a twinge of nostalgia to me.
[QUOTE=Master Chris;30024442]Well hopefully you won't have to anymore, apparently valve have tracked down the cause of the issue and it should be updated fairly soon: [url]http://www.youtube.com/watch?v=Ii1tyVeIePY[/url][/QUOTE]FINALLY! Thank you so much.
I think it just got fixed with this latest engine update from valve, i removed the -r_worldlights 0 from my launch options in all of the effected games and so far everything that use to do it shows up fine now.
YAY. about darn time
Yes! YES!!! About time too...
phongs are now fixed so this thread is over
It's finally fixed!! Hooray!
My sincere thanks to Garry for looking this up and seeing if he could fix it, and to Valve for going out of their way to fix this for us. It's very appreciated and I'm glad our patience got rewarded!
So yes, this can be locked now. Issue fixed!
Sorry, you need to Log In to post a reply to this thread.
