9 replies to this topic

[Noah Fentz]

I just finished playing a few games of melon's Fish Tales, and I was really intrigued by one major difference between this table and many recent releases ...

Everything was in the correct order, and I didn't have to 'Bring to Front' every object to fix missing or out of order plastics.

So, I have to ask ... what is it that others are doing that melon didn't in their table designs?

I suspect it's the use of 'Draw in Back' and 'Draw in Front' when designing, but unless we find out what it is specifically, then I would have assume this can't be fixed. I never had this problem until the last couple of versions of VP, so I know it's 'fixable'.

Am I the only one experiencing this?

[faralos]

I have never experienced anything having to do with the 'draw in front or back' and honestly never noticed it in building originals either, until your post. I do get the occasional crash with vp9.5 (due to that HD box being checked on some newer tables)and can't even get 9.7 to run at all, but other than that, no problems here. But then again ALL the newer (real busy playfields) tables don't run on my computer I guess the integrated graphics just can't handle stuff like fading lights or multiball

[Rawd]

I didn't have to 'Bring to Front' every object to fix missing or out of order plastics.

Am I the only one experiencing this?

I have never experienced this.

[destruk]

I did once on your Getaway table, with the inlane decals. Otherwise, no.

[Noah Fentz]

I know I'm not the only one. Clickersnapper has also mentioned it before, and UR also has this problem.

Here's a screenie of UW's Xenon as rendered by my 9500GS (I know, not the greatest card, but this is a new issue. Didn't happen before 905) ...

[melon]

I just finished playing a few games of melon's Fish Tales, and I was really intrigued by one major difference between this table and many recent releases ...

Everything was in the correct order, and I didn't have to 'Bring to Front' every object to fix missing or out of order plastics.

So, I have to ask ... what is it that others are doing that melon didn't in their table designs?

I suspect it's the use of 'Draw in Back' and 'Draw in Front' when designing, but unless we find out what it is specifically, then I would have assume this can't be fixed. I never had this problem until the last couple of versions of VP, so I know it's 'fixable'.

Am I the only one experiencing this?

Hi.
About the missing or out of order plastics, I have never experieced this in my computer (it's a crappy P4 with a 7600GS) but I do have noticed it in some tables in my pin cab (with a 9500GT), so it may be a GFX or driver issue?
Anyway, in my tables I dont use Draw in back or draw in front when designing. If I want to change, lets say a plastic, and there is a ramp above it, instead of making "draw in back" to the ramp so I can modify the plastic, I translate the ramp, then I modify the plastic, and then I translate back the ramp, so everything keeps in the order I designed it. I don't know if it has some real effect to the table, but I prefer working this way.

[Noah Fentz]

... in my tables I dont use Draw in back or draw in front when designing.

Yeah, I'm rather convinced this has the most to do with the problem/solution.

EDIT: Updated to the latest drivers from 182.xx and still, the problem persists.

[unclewilly]

I have never had the issue on any table that's why I do use the draw in back on occasion. I would assume since it only happens on certain peoples systems it would be a hardware or direct x issue. I have a 9800 gtx+ and a 260 gts and have never had the issue. doesn't the reorder checkbox in the editor take care of reordering stuff in the proper order?

[faralos]

Hi.
About the missing or out of order plastics, I have never experieced this in my computer (it's a crappy P4 with a 7600GS) but I do have noticed it in some tables in my pin cab (with a 9500GT), so it may be a GFX or driver issue?
Anyway, in my tables I dont use Draw in back or draw in front when designing. If I want to change, lets say a plastic, and there is a ramp above it, instead of making "draw in back" to the ramp so I can modify the plastic, I translate the ramp, then I modify the plastic, and then I translate back the ramp, so everything keeps in the order I designed it. I don't know if it has some real effect to the table, but I prefer working this way.
[/quote]


you say a crappy P4, well I am using an even crummier p3! with intel integrated graphics ( a Dell, no less!) and many of the newer tables (fading lights, more than 3 multiballs, etc.) and none of them will run without serious stuttering, but I have never seen that in front/back problem yet even on the ones that don't play on my sytem at all

Edited by faralos, 11 June 2010 - 06:29 PM.

[Noah Fentz]

Okay, well, this is going to sound like madness, but here's what I just did in Xenon ...

I unlocked all the PFOn dropwalls and drew them in FRONT, and it resolved the issue for those. I still have to fix the lights along the tube, somehow.

Also, other than that, I usually have to copy every gate object, delete it, paste it, and (possibly) rename it to the name in the script.

Looks like I need to upgrade my vid card, but the odd thing here is that it only started recently for me. Always been the case for UR.