2087 replies to this topic

[bent98]

Ok,

 

Test 5 has a major graphics issue. Check out airborne. If you look at the apron you can see it easily. I gave you comparison photos for airborne. Tpo one is what its supposed to look like. I also included worldcup soccer as its more apparent on that  table. Keep in mind the apron isnt the only area thats affected but its just easier to see.

WCS is Body dumps mod and airborne is body dump/JF version.

 

Also, another weird thing. Test 4 seems to be working now with no graphics issue on airborne over  Win XP. I did nothing different. Wondering if a reboot was all that was needed ?

 

 

 

[kruge99]

Medusa 1.0 by PacDude is fixed!  but Centaur 1.2 by PacDude has some black gates still.  Great progress Mukuste!!!

[mfuegemann]

Hi Les73gTx,

 

thank You for the explanation, that explains the dramatic drop to ... my refresh rate ...

Although I noticed some micro stutters with active vsynch on with no impact to the shown 60 fps.

 

@bent98:

 

I think Your graphic glitches are the same transparency issues I noticed on my decals.

 

Regards

Michael

 

P.S.: mukuste, Your speed of improving the project is incredible. Thank You for this!

Edited by mfuegemann, 22 February 2014 - 02:28 PM.

[kiwi]

As has been mentioned above, pure black is transparent.
Via scripts or from property of the bumper, the state of the bumpers  "On" , does not work, it is always Off.

Blinking or "Flash When Hit"  is OK.

 

Thanks

 

Max

[mfuegemann]

Hi kiwi,

 

I missed the post stating 0/0/0 is transparent per default. This is fine with me.

 

Regards

Michael

[kiwi]

Hi kiwi,

 

I missed the post stating 0/0/0 is transparent per default. This is fine with me.

 

Regards

Michael

With static objects, in VP9, pure black is not transparent,
is transparent with non-static objects (Lights, DropTargets).

 

Max

 

Edit : "As has been mentioned above, pure black is transparent."

I meant the Bent98 post.
We have posted the same time.

Edited by kiwi, 22 February 2014 - 03:01 PM.

[bent98]

I also notice something that was introduced in test version 4 and remains in version 5. Below is screenshots of WCS mod by Body Dump.

 

This is what the ramp is supposed to look like. (works in test Versions 1,2,3)

Look at the ramp. Theres gaps at the edge of the ramps.

 

[zany]

From now....i made VP DX9 to my primary VP!
There is just some minor bugs as mentioned....like this:

 

Attached Files

•  abrcad_postit.jpg   41.75KB   7 downloads

[zany]

...also..that black/transparency issue.

[skinooe]

thanks very much. Tables looks awesame. And the Flash lights are soo cool.Some ramps have very little vibration.

Is it possible that the fahser immerse the area in the colors of flasher?

Thanks for your great work!

[DJRobX]

Also, another weird thing. Test 4 seems to be working now with no graphics issue on airborne over  Win XP.

Whatever that texture issue is, it's "random".   The blotch changes in shape.   Sometimes it's visible, sometimes it's not.    TZ Megapin has the same problem.     Behavior suggests that something is operating on uninitialized memory.    Probably never reproduces in a debug build

 

Mukuste - I tried to take a stab at finding this issue since you're having a hard time reproducing, but I can't build your source.   It's missing 'Material.cpp' and there are various other errors, for example:

 

textbox.cpp(286): error C2039: 'RenderMovers' : is not a member of 'Textbox'
1>          r:\source\vpdx9\vp9_dx9_test5\textbox.h(27) : see declaration of 'Textbox'
1>textbox.cpp(290): error C2065: 'm_pobjframe' : undeclared identifier
1>textbox.cpp(293): error C2065: 'm_d' : undeclared identifier

 

You might want to check that what's in github is cohesive.   

Edited by DJRobX, 22 February 2014 - 04:41 PM.

[Horrible]

I spent last night playing with v4 and was getting DMD moves and resizing either to the primary screen (3 screen setup) or around the backglasses.

I was also getting problems on the T2 chrome table T2_chrome_fs_b2s where black lines were appearing all over the table (edges of graphical elements), any movement of the flipper opened up gaps in the graphics also.


I've tried 10 or so tables with v5 and am not getting any of these problems. I'm enjoying the playing so much that I haven't noticed any glaring issues ( from your average users perspective).


All I can say is that it is starting to look like the dogs dangly bits!

We'll done, really impressive.

I hope all the technical fine details (that are appearing this forum and frankly I don't fully understand) can be ironed out so we can get a final release version.

Thanks again for all the hard work being done so far, much appreciated.

[tttttwii]

Fatal error on Rocky and Bullwinkle: Starting this table I get error in the rendering device:

 

Fatal Error: HRESULT 8007007e at ..\RenderDevice.ccp:342

 

I am running Win7 64bit, 4GB memory and Nvdia GTX760 2GB, I only observed this in Rocky & Bullwinkle. All other tables are running fine. Can you help?

Edited by tttttwii, 22 February 2014 - 06:38 PM.

[mukuste]

Thanks again Mukuste for your work! One question: Would it be possible to add higher resolutions to the "windowed fullscreen"? Just got myself a 2560x1440 monitor and now the 1920x1080 windowed mode doesn't cover the whole screen anymore... Of course only if this is easy to implement.

 

Right now it always uses the primary monitor to obtain the screen size. So I guess that monitor isn't your primary one? Multimonitor support is on the list.

 

 

 

mfuegemann:

- Transparency calculation is not right (Transparency set to 2/0/0 and colors 0/0/0 are shown as transparent)

 

Can you explain a bit better what you mean? I don't understand.

 

 

Ok,

 

Test 5 has a major graphics issue. Check out airborne. If you look at the apron you can see it easily. I gave you comparison photos for airborne. Tpo one is what its supposed to look like. I also included worldcup soccer as its more apparent on that  table. Keep in mind the apron isnt the only area thats affected but its just easier to see.

WCS is Body dumps mod and airborne is body dump/JF version.

 

Also, another weird thing. Test 4 seems to be working now with no graphics issue on airborne over  Win XP. I did nothing different. Wondering if a reboot was all that was needed ?

 

 

 

Yeah, Airborne and TZ have known issues on XP, I have no idea why. Maybe DJRobX can uncover something, I don't have an XP machine. The only thing I can tell you is to update to the latest drivers and see if it fixes the issue, it might be a driver problem.

EDIT: Actually, hold on.... at least the Airborne issue I can reproduce if I run the release build, RobX was spot on there... still no idea what's wrong, though.

 

 

 

From now....i made VP DX9 to my primary VP!
There is just some minor bugs as mentioned....like this:

 

 

What table is that?

 

 

...also..that black/transparency issue.

 

What is that issue?

 

 

 

Also, another weird thing. Test 4 seems to be working now with no graphics issue on airborne over  Win XP.

Whatever that texture issue is, it's "random".   The blotch changes in shape.   Sometimes it's visible, sometimes it's not.    TZ Megapin has the same problem.     Behavior suggests that something is operating on uninitialized memory.    Probably never reproduces in a debug build

 

Mukuste - I tried to take a stab at finding this issue since you're having a hard time reproducing, but I can't build your source.   It's missing 'Material.cpp' and there are various other errors, for example:

 

textbox.cpp(286): error C2039: 'RenderMovers' : is not a member of 'Textbox'
1>          r:\source\vpdx9\vp9_dx9_test5\textbox.h(27) : see declaration of 'Textbox'
1>textbox.cpp(290): error C2065: 'm_pobjframe' : undeclared identifier
1>textbox.cpp(293): error C2065: 'm_d' : undeclared identifier

 

You might want to check that what's in github is cohesive.   

 

 

Thanks for trying to help track this down! The Github is cohesive, but the VS project files might not be since I don't use them, so I would recommend using CMake to regenerate whatever version of solution you need.

 

Also, make sure the VPINBALL_DX9 define is set (the CMake file should take care of that, but double check in case you still have problems).

 

 

Fatal error on Rocky and Bullwinkle: Starting this table I get error in the rendering device:

 

Fatal Error: HRESULT 8007007e at ..\RenderDevice.ccp:342

 

I am running Win7 64bit, 4GB memory and Nvdia GTX760 2GB, I only observed this in Rocky & Bullwinkle. All other tables are running fine. Can you help?

 

Hm, that's when it's trying to compile a shader. Two things to try: (1) disable FXAA/3D (2) do a complete installation of DirectX 9.

Edited by mukuste, 22 February 2014 - 07:12 PM.

[mfuegemann]

Hi mukuste,

 

I have decal images with transparency set to 2/0/0 (R/G/B). When I start the table this color and the pure black (0/0/0) is shown as transparent. I want the 0/0/0 to be transparent only if specified at the image settings.

 

Regards

Michael

[mukuste]

Hi mukuste,

 

I have decal images with transparency set to 2/0/0 (R/G/B). When I start the table this color and the pure black (0/0/0) is shown as transparent. I want the 0/0/0 to be transparent only if specified at the image settings.

 

Regards

Michael

 

People told me that pure black was transparent in VP9, so I made it like that. It's part of the solution to the black insert lights and so on. You'll have to work around that by setting the black areas to 1/1/1 or something like that.

[htamas]

The black playfield light problem is indeed fixed in TEST5. Great!

I can still get occasional crackling in the ROM sounds, compared to the DX7 version, but if nobody else experiences this, then it's possibly related to my hardware.

 

Hook still exhibits the same issues (flashing / black playfield, lines on apron) like before. I also noticed that there is some problem with rendering the skill shot area above the plunger lane. It looks like this is related to the mentioned black / transparency issue because what is black in DX7 seems to be transparent in DX9.

This table is the only one so far where I noticed the same slight stutter like in the DX7 version. All other tables perform really great. So the stutter may be related to how the table was built; it never played too well for me.

[mfuegemann]

Hi mukuste,

 

as stated before I can live with that and rework my images. Although it is not the case in VP9. There You can set the transparency color for each picture (if the VP is saving the specified value).

Often 2/0/0 or 0/255/0 or 255/0/255 are used as well as 0/0/0 for transparency.

 

Regards

Michael

[DJRobX]

Thanks for trying to help track this down! The Github is cohesive, but the VS project files might not be since I don't use them, so I would recommend using CMake to regenerate whatever version of solution you need.

 

Ah, I see, thanks.   With that, I got it to build successfully.   I've never used CMake, but there are only a few things I needed to change in the solution to make it build.  (VPINBALL_DX9, dinput8 instead of dinput, add nvapi.lib, remove dead reference to Material.cpp and add hash.cpp file).    Now the real fun begins

[Horrible]

Just to note.

I've had a go on airborne and I'm getting the same issue on the apron as bent98.

I have tried two versions of Rocky and Bullwinkle, no crashes, but the ball was flickering and appearing translucent on the play field around the flowers, as well as the side lanes.