1394 replies to this topic

[toxie]

Dunno, i didn't add this..

[jpsalas]

About the new light option: If I don't use images, the on state just becomes white. With images is the same as before, or at least I can't see any difference.

[toxie]

It should be slightly brighter..

[jpsalas]

Yes, I see it now, it is slightly brighter and is good The lights can't never be bright enough

[ryukoken]

it crash for me under win7sp1 and winXP SP3 since rev525

 

Signature du problème :
  Nom d’événement de problème:    APPCRASH
  Nom de l’application:    VPinball rev561.exe
  Version de l’application:    9.1.6.0
  Horodatage de l’application:    5185f50d
  Nom du module par défaut:    D3DIM700.DLL
  Version du module par défaut:    6.1.7600.16385
  Horodateur du module par défaut:    4a5bd9ab
  Code de l’exception:    c0000005
  Décalage de l’exception:    0002cd1f
  Version du système:    6.1.7601.2.1.0.256.1
  Identificateur de paramètres régionaux:    1036
  Information supplémentaire n° 1:    0a9e
  Information supplémentaire n° 2:    0a9e372d3b4ad19135b953a78882e789
  Information supplémentaire n° 3:    0a9e
  Information supplémentaire n° 4:    0a9e372d3b4ad19135b953a78882e789
 

[toxie]

what gfx card do you have?

do you have hardware rendering in the video options enabled?

 

 

@JP: it should be much more different as soon as you use the new lightsource options (like if you use pointlights instead of directional lights, or if you decrease the brightness or change the colors of the two lightsources)..

[Practicedummy]

Something I want to add as far as a 'feature' goes. I should have mentioned this a lot sooner but kept putting this off. When I use the Tab key to cycle down the properties panel on VP, it will only cycle through a category and then repeat, instead of cycling though all the properties. Example, on Ramp properties, I start cycling through Top Height, Bottom height etc.. and then after Right Wall when I hit the Tab key again, instead of going to Left wall (Physical Wall), it cycles back to Top Height (Position).

 

This gets a bit annoying as I am used to using the Tab key to cycle through EVERYTHING in all other programs and applications. Can this be fixed? Thanks in advance!

[jimmyfingers]

The new option for disabling the lightsources effects on light objects "Old/darken 'On Image' lighting" is causing side effects on other objects when it is enabled on any light object (lamps, table / PF GI, etc.). As you will see in the screen captures, it causes the flippers and other objects to turn white. Whether I have the general lightsources settings enabled and configured or left as default / blank, as soon as I change this setting on even just one light object, the glitch still is present. It also seems to disable the lighsources effect on some other objects that I did not choose, like in the below pictures the plastics lighting objects were effected after only setting the PFGI to clear that option.  These captures were taken with the lightsources with default base settings but with a point light (2) created for L1 type with L1 POS XYZ as 500,1000,500 It occurs on both of my systems (Windows 7 32-bit, Nvidia drivers 306.97). I've also tested it with combinations of the Region Updates and (FX)AA optimizations enabled and with AA off and forced on - same result in all cases. Here are two screen captures with it enabled on the PFGI and with it cleared (to not have the lightsources options / effects applied to that light object):

 

 PB Lightsource Capture 1.PNG   1.07MB   113 downloads

 

 PB Lightsource Capture 2.PNG   1.12MB   111 downloads

 

The new lightsources feature seems to be able to add some nice ambiance so I'm hoping it can be sorted to work without affecting the other lighting objects and without these odd side effects.  As always, thanks for your work furthering VP and your keenness to add features and resolve bugs.

Edited by jimmyfingers, 07 May 2013 - 07:28 PM.

[toxie]

which rev did you use, cause there was a bug introduced in 560 (and fixed again in 563)..

[unclewilly]

I appreciate all you guys are doing. Just curious, are you still working toward dx9 implementation

[fuzzel]

hehe yes slowly

VP code is a mess and the complete program was never designed to support different render APIs. Everything is defined for DirectDraw and DX7.

We're reorganizing the code so it's easier to switch to DX9. The increase of the FPS since 9.14 has to do with those reorganizations, but of course not all of them

It will definitely take a lot more work/time until we can even think of switching to DX9

Edited by fuzzel, 08 May 2013 - 04:19 PM.

[Slydog43]

Thanks for all your work, it really is appreciated!

[LoadedWeapon]

Yes! Thank you very much..Vp getting better all the time  

[ryukoken]

what gfx card do you have?

do you have hardware rendering in the video options enabled?

i have an old ati x1650 series (i know it's a jurassic card)

it crash without hd rendering but it to slow with , it's why i

disable it, its work fine without hd with rev525

After this build all are crashing under seven or xp

[htamas]

This is exactly the reason why there should be a minimal hardware requirement specification for VP and why HD rendering should be an absolute must.

[toxie]

what gfx card do you have?

do you have hardware rendering in the video options enabled?

i have an old ati x1650 series (i know it's a jurassic card)

it crash without hd rendering but it to slow with , it's why i

disable it, its work fine without hd with rev525

After this build all are crashing under seven or xp

 

Unfortunately i guess we'll have to abandon these very very old cards over time..

Especially as used, but still very good cards are already available for a few bucks..

[bent98]

Time to upgrade your card

[oooPLAYER1ooo]

Still getting issues with vp having to be reset when ramp added its not rendering it its like its caching table and ignoring new ramps

Also seem to be getting more corruptions with 4 sided primitives with latest builds since rev548

Edited by oooPLAYER1ooo, 09 May 2013 - 03:06 PM.

[toxie]

Yup, i know.. That hasn't been fixed yet, but i think it's due to the changes with the vertex buffers, they don't get updated properly.. Maybe i can look into it tomorrow..

[oooPLAYER1ooo]

Thanks toxie