search

thoth23 / fpscreatorengine

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

invisible stock segments #58

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. turn on full shaders
2. build test game
3.

What is the expected output? What do you see instead?
I expect to see segments
segments are invisible

What version of the product are you using? On what operating system?
v118 beta9 
have tested with a build of latest source and error still present

windows xp sp3
nvidia 6600gt 
1gb ram
2.8ghz single core

Please provide any additional information below.

tested with v117 and worked without error
attached fpm file and setup.ini
and image showing error

have updated directx9 and graphic drivers to latest

Original issue reported on code.google.com by tinyp...@gmail.com on 28 Feb 2011 at 11:38

Attachments:

GoogleCodeExporter commented 9 years ago 
Works in BETA10 here. Try running the FPSC cleaner and then building the level 
from scratch and try again. Thanks. Can anyone else confirm this happens with a 
nvidia 6600gt (to discount this as a possible cause).

Original comment by LeeBamberTGC@gmail.com on 28 Feb 2011 at 1:58

GoogleCodeExporter commented 9 years ago 
Sorry,I should have said that I have been running the cleaner between each 
build as I originally thought this was the cause and the problem is still there.

Original comment by tinyp...@gmail.com on 28 Feb 2011 at 3:59

GoogleCodeExporter commented 9 years ago 
same here ...integrated inlet media graphic media accelerator 3100

Original comment by veeru565...@gmail.com on 3 Mar 2011 at 8:54

GoogleCodeExporter commented 9 years ago 
same issue using a Ati 5670 card

Original comment by senig...@aol.com on 7 Apr 2011 at 5:07

GoogleCodeExporter commented 9 years ago 
here too! nvidia geforce 9500GS

Original comment by mazzella...@gmail.com on 8 Apr 2011 at 8:18

GoogleCodeExporter commented 9 years ago 
Finally fixed for BETA13. You would not BELIEVE what I had to do to reproduce, 
then FIND the code causing this one. Don't even ask!!

Original comment by LeeBamberTGC@gmail.com on 13 Apr 2011 at 2:20