poser problem...

[ruby_sauce]

can someone please help me? I have a problem with poser:

(images are a little large, thats why I put them in spoiler boxes)

Spoiler :

Spoiler :

I don't know how to solve this. can someone please help me?

 

[Waldtroll]

What did you do before this occured?

 

[ruby_sauce]

I had some trouble with a game, I needed to update drivers. something went wrong there, but I restored everything with that option.

oh wait a minute, could it be because I updated my video driver?

that is the only thing that I did different...

but how could I fix it then? get my old driver back? but I want to play the game, too (this isn't civilization, its another game)

 

[Bjornlo]

Perhaps Poser uses OpenGL, most 3d apps do. This would be part of the video driver. Did you use a WHQL driver?

 

[Vuldacon]

Looks like your Driver Update changed some settings or is lacking what is needed. Poser Uses OpenGL Hardware as well as SreeD software for renders.

Type "OpenGL Hardware Acceleration" in Poser Help to read more, on Page 102.

Try Right Clicking in the Preview Screen in Poser and select Hardware or Software Rendering. Hardware Rendering uses OpenGL and Poser Detects if your system has it...IF not, you can use Software, which is SreeD Rendering. Hardware Renders are far better and you also have control over the Render size where it does not require being the same size as the Preview window.

...First check your Render settings to gain more insight but your Screenshots appear to be lacking the ability to Use OpenGL. Check your New Driver and make sure it has OpenGL...you might need a different Updated Driver.

 

[Plotinus]

I've never seen anything like that before.

However, to get Poser to work on my computer at all, I have to turn the hardware acceleration right down. Perhaps this will help you too:

Right-click on your desktop. Choose the Settings tab. Click the Advanced button. Choose the Troubleshoot tab. Move the slider on Hardware Acceleration to the last but one position on the left.

 

[ruby_sauce]

well, I tried plotinus's option first (because it seemed easiest to do >_<. I am not that good with computers on some things...), wich seems to have solved the problem of the weird pixel thing.

I got something else, wich he also does when I make a new unit, and try to put clothes on it (he doesn't do this while rendering, but it is annoying if I want to texture the clothes):

Is this also caused by the video driver? also, I don't know how to check if my driver has openGL

Spoiler :

 

[Virote_Considon]

Use the front camera. It looks like that when I use the main camera, too. The Front Camera is not perfect, but it is miles better

EDIT: A picture speaks a thousand words (even if it is a .jpg):

 

[ruby_sauce]

oh yeah, you are right . I can use the front camera to check textures...

but no one knows what causes this?

 

[Virote_Considon]

Not to my knowledge. All I know, is that it is a problem which only seems to affect the main camera preview- it still renders fine! (Although when rendering the N direction, you'll probably want to set it to -180 degrees, not 180 degrees )

 

[Plotinus]

You're just zoomed too far out. Poser has difficulty with surfaces that are close to each other when rendering previews. So it shows skin instead of clothing and so on. The closer in you zoom, the more correct it is.

You ought to make body parts that are entirely covered by clothes - such as his abdomen, chest, and shoulders in this case - invisible anyway. That makes rendering quicker, and it looks better in the preview screen.

 

[ruby_sauce]

but before I looked at it from the same distance, and it would just view normal...

 

[Vuldacon]

Good Points from Plotinus and Virote_Considon but I still believe it is your Graphics Card Driver Update that has caused the problem. I never have any problems viewing clothing with the Main Camera in Poser.

The Driver may be OK but something may have gone wrong with the installation.
IF you were able to view clothing ok with the Main Camera before the Update and now you cannot, it is probably the Driver or installation of it that is causing problems...Check with the people where you obtained the Driver for information about it.

 

[Bjornlo]

I too think it can be fixed with the right driver. A messed up openGL driver can really do some strange things. And, it all worked before you installed the latest video driver, right?

You never answered me before. Did you use a WHQL certified driver? This is important. Certified drivers are more stable and far less likely to mess up.

 

[ruby_sauce]

Assuming things worked before, I too think it can be fixed with the right driver. A messed up openGL driver can really do some strange things.

You never answered me before. Did you use a WHQL certified driver? This is important. Certified drivers are more stable and far less likely to mess up.

where can I see it I have a WHQL certified driver? I just got mine of the ATI website...

if it matters, I have an ATI radeon 9800 series...

 

[Vuldacon]

WHQL is an acronym for Windows Hardware Quality Labs. They Test Driver performance.
When you installed the Driver, did you get a warning message that the Driver was not signed?

 

[ruby_sauce]

WHQL is an acronym for Windows Hardware Quality Labs. They Test Driver performance.
When you installed the Driver, did you get a warning message that the Driver was not signed?

I didn't get a pop-up error or something. I ran the setup, had to select the folder where to install it, and agree to stuff ans such. no warning messages occured.

 

[Bjornlo]

WHQL drivers are typically marked as such. ATI partnered with Microsoft a while ago and had developers in Redmond to improve their driver quality, and for a while at least (not sure about today since I left 2 years ago) all ATI drivers where WHQL. The drivers which do not cause Windows XP to give a warning are normally WHQL drivers. But it is possible to have a driver "signed" but not be up to WHQL standards. All vista drivers have to be signed and I seem to recall that the signing processes for Vista was more strict and they might well have to pass WHQL to be signed. With XP a larger company is allowed to sign the drivers themselves if they "promise" that it is a good, stable and tested driver.... but these signed but non-WHQL drivers were a bit of a problem since people like Creative Labs, Canon and some others had quite different ideas on what was good enough to be signed.


What feature was missing in your old drivers that you had to replace them?

 

[ruby_sauce]

WHQL drivers are typically marked as such. ATI partnered with Microsoft a while ago and had developers in Redmond to improve their driver quality, and for a while at least (not sure about today since I left 2 years ago) all ATI drivers where WHQL.

What feature was missing in your old drivers that you had to replace them?

Well, whenever I tried to play Lineage 2 I could log in, but I couldn't get to my characters. because when I pressed the button to do so, the PC would freeze for about 15 seconda and I would get an error message something like:

"error with ati2dvag.dll". I googled and found that I needed to update my video driver software. so I did and now it works...

 

[Bjornlo]

Rats you quoted me while I was editing my post. Oh well...

What video card are you using?