Age Verification
This website contains age-restricted material including nudity and explicit content. By entering, you confirm being at least 18 years old or the age of majority in the jurisdiction you are accessing the website from.
I am 18+ or older - Enter
I am under 18 - Exit
Our parental controls page explains how you can easily block access to this site.

Últimos mensajes - Página 1616

  Foro

EverthangForever
Desde en Oct 2009
4483 posts

Discussions for Scenes for Version 1.2.X Fullscreen Mode here

Todo sobre iStripper
November 17, 2016, 5087 respuestas
Now that we have to rely on vghd.log for fault finding, it raises a few concerns I'm having about either my Geforce XTG 660ti Nvidia GPU card or bugs in the efficiency of the iStripper fullscreen platform.

I have the latest NVidia drivers & my rig seldom if ever crashes. I am generally happy with the performance overall. However the number of reported false starts and incorrectly identified or assigned node characteristics for animate: in the vghd.log gives me cause for concern. Could it be bugs in the programming of the platform I wonder:-/ ??

For instance: wrt to animation: cycle time, repeat mode, movement curve, property, amplitude

Ran some test scenes which I had thoroughly checked the .scn code for and cannot find syntax errors.
Inspite of this I often get the following errors reported:

fullscreen WARNING[Unknown curve "pingpong" for node ""]
fullscreen WARNING[Unknown curve "0" for node ""]
fullscreen WARNING[Unknown repeat mode "0" for node ""]
fullscreen WARNING[Unknown node property "source"]
fullscreen WARNING[Unknown node property "ambient"]

also I'm getting lots of:

vhd WARNING[WMVCore isn't available (Using FFmpeg as a fallback)...happening on every use
WARNING[libpng warning: iCCP: cHRM chunk does not match sRGB]
WARNING[libpng warning: iCCP: known incorrect sRGB profile]

Just wondering if others are getting similar reports in their vghd.logs ?
And does it matter ?