Shader problems possibly? idk?
uhm... im a 1.16 and im very interested in coming into 1.32. I've recently downloaded this mod since it seems so completely bad ass compared to .16 noghost, and also i have downloaded defrag. Both of which give me a similar problem that does not exist in 1.16 or a regular q3 servers in 1.32. heres what it looks like =/
the railgun also looks like that gray matter, and in defrags case, rockets leave behind a gigantic trail of grey squares. I dont know jack shit about this sorta thing so could someone please help me out?
uhm... im a 1.16 and im very interested in coming into 1.32. I've recently downloaded this mod since it seems so completely bad ass compared to .16 noghost, and also i have downloaded defrag. Both of which give me a similar problem that does not exist in 1.16 or a regular q3 servers in 1.32. heres what it looks like =/
the railgun also looks like that gray matter, and in defrags case, rockets leave behind a gigantic trail of grey squares. I dont know jack shit about this sorta thing so could someone please help me out?
Do u use the same cfg for all the mods?
He wats this?
Have you radeon Grafikcard?
He wats this?
Have you radeon Grafikcard?
nope cant be radeon or you would see the best graphics known to man
wrote:He wats this?
Have you radeon Grafikcard?
nope cant be radeon or you would see the best graphics known to man
nope cant be radeon or you would see the best graphics known to man
Maybe after you've gotten past the gamma bugs... I'm never buying an ATI again until they sort out their miserable drivers. :roll: Back to nVidia as soon as I have the money. Anyways, getting back on topic...
im wold suges u have damaged pk3 files somwhere
Let's clarify what "damaged PK3" files can mean... If its a install off the CD, then the other most likely problem is a different pk3 file in your baseq3 dir which is overwriting the base textures with its own. If you dont have that many custom maps installed, just try moving all the pk3 files to another directory (everything except pak0..pak8) and then put them back one by one until you see which one is causing your problem.
i dont believe that it has to deal with hardware problems because the excessive-plus mod i believe comes with its own custom rocket trails or whatever and i can see them fine. Defrag uses the same rocket trail as regular 1.32 and i cant see that one. So - since this is the ase i think that something is facked up to oblivion somewhere =o.
To answer the first post, yes - i do use the same configuration for 1.16 as i do 1.32 (defrag regular q3 and EP). Maybe it has something to do with this =?, if so, the only way to troubleshoot the issue would be for someone to send me a functional Excessiveplus config?
Plus - if someone knows exactly what those boxes have in common then i think that could help identify what exactly there is a problem with. Like... specifically - does anyone know what q3 actually puts on top of those grid-like boxes in the screenshot? They are used to draw the weapontrails, the explosive-looking excessive-plus thing (you can see all the little small shrapnel boxes in the screenshot) and also on the edges of the map where its the same grid?
I hate to come into such a cool community looking like a fool causing problems :oops: I'll have you all know that i'm lookin forward to actively participating in this mod for 1.32 since it seems so superior to the other facked up gamestyles ive seen. (like that rail and hook crap that RnR plays lol =S)
Once again - any post helps and all are definately appreciated. Every1 in the 1.16 community would call me stupid and dismiss me right off the bat but ya'll are bein pretty kick ass so thanks