3889 replies to this topic

[atarian]

I don't know about others but all this talk of eggs is making me hungry .

[fuzzel]

Well finding good backdrop settings is always a pain and I doubt that there is an easier way if you want the freedom to adjust everything and you have to adjust everything because every table is different. Actually the layback is evil because it screws the whole scene and that's the reason for the egg ball. It's better to play more with the inclination, z-offset and FOV and don't raise layback over 70 better is to have it around 50.

[Shoopity]

Forgive me as I'm not sure the best place to say the following since VPX is out in the wild now (I don't know if the VP10 dev thread is still that active); also forgive me if this has already been suggested and/or is on the roadmap already:

Would it possible (or even a good idea) to have some sort of automatic script update capability?  Maybe an author can put a line of code in the script that let's VP know where to look for a .vb file (e.g. Drop Box, Google Drive, etc.), have VP check if that file name has a higher number than the current one (so it would be up to the author to name the script file correctly), and prompt the user if they wish to update the code?

 

This way an author can provide updates to their table (whether it be bug fixes, or even new features) without forcing a re-download of the whole table.

[freneticamnesic]

Alright great info on the AA ... with all antialiasing off, I get 190fps smooth. With nvidia enabled fxaa on I get 110fps smooth. This is much better. And a sweet new bloom effect....

[atarian]

Well finding good backdrop settings is always a pain and I doubt that there is an easier way if you want the freedom to adjust everything and you have to adjust everything because every table is different. Actually the layback is evil because it screws the whole scene and that's the reason for the egg ball. It's better to play more with the inclination, z-offset and FOV and don't raise layback over 70 better is to have it around 50.

Yes having all the config options is what makes VP so good, and we wouldn't want to lose that. From the last few posts we can see that with some simple tweaking the ball can look correct .

Only an idea but maybe for some way in the future update the user could select different 'View params sets' from a drop down (like physic sets) so authors could define multiple views.

Edited by atarian, 12 February 2015 - 06:50 AM.

[BananaBoat]

Alright great info on the AA ... with all antialiasing off, I get 190fps smooth. With nvidia enabled fxaa on I get 110fps smooth. This is much better. And a sweet new bloom effect....

Yes, I see the same results.
Still tho, not sure why monster bash has a jerky ball on my system, vsync settings perhaps? Mine is default at zero.

[fuzzel]

Forgive me as I'm not sure the best place to say the following since VPX is out in the wild now (I don't know if the VP10 dev thread is still that active); also forgive me if this has already been suggested and/or is on the roadmap already:

Would it possible (or even a good idea) to have some sort of automatic script update capability?  Maybe an author can put a line of code in the script that let's VP know where to look for a .vb file (e.g. Drop Box, Google Drive, etc.), have VP check if that file name has a higher number than the current one (so it would be up to the author to name the script file correctly), and prompt the user if they wish to update the code?

 

This way an author can provide updates to their table (whether it be bug fixes, or even new features) without forcing a re-download of the whole table.

That's not planned at the moment. However there is a patching system for VP9 available on the other side afaik. I think it will be updated for VP10 once VP10.0 is final.

[fuzzel]

rev1686 is up:

 

- ball anti-stretch feature was improved in a way that the ball is more round in the upper area of the playfield

- flasher issue fixed if you use two images

[BananaBoat]

do we need to update the script files each update or will just the .exe suffice?

[fuzzel]

I will mention that if you have to update the scripts so updating the exe is enough.

[chepas]

rev1686 is up:

 

- ball anti-stretch feature was improved in a way that the ball is more round in the upper area of the playfield

- flasher issue fixed if you use two images

 

Nice, so using 2 flasher images the other day was the cause of all the pink lines?

[fuzzel]

I don't know of any pink lines but in the previous version the second image was overwritten with a builtin environent map and not the actual defined image B

[chepas]

Yes, I see. This is what I meant here. Looks the same as you described.

 

http://www.vpforums....=30418&p=296745

[cyberpez]

Hi there,  I've been working on converting over my New Wave table to VP 10 and ran across a bug, maybe.  I have the feeling it has to do with overheating of my video card, but thought I would throw it out there.  I first ran across it when I created a "clear plastic" material.  It was pretty much just a grey plastic material with an occupancy of 50%.  I added the first 5 or so and then after that I got this grey blob whenever I would play the table.  I just started adding them as the default metal and was able to continue on.  If I changed any of the plastics back to the "clear plastic" the blob would come back.  I let things set for a day or so and when I came back I was able to change the plastics back to the "clear plastic" with no blob.  I figured an update fixed the issue.  Well, I was working a bit more last night and the issue came back.  This time I changed the "plastic with an image" material to 90% occupancy and the blob came back.  Unchecking apply and it goes away.

 

Also,  I have a "grey haze" over the whole table..  backdrop and all.  I thought I read earlier in the thread on how to fix that, but whatever I remembered it being was not the fix.  The papa smurf table looks fine.  Any ideas?

 

as for vp10 I'm digging it so far 

 

-cyberpez

 

 

Attached Files

•  vp10 grey blob.png   253.46KB   24 downloads

[unclewilly]

Not sure about the blob.

For the haze over the whole table.
look in the lightsource options. The very top color needs to be set to pure black 0.0.0. Just click on the color and change it and the haze will go away

[sliderpoint]

The blob doesn't really look like a video card heating issue, It looks like an object.  Is there some random object that is maybe part of a collection that gets selected when you click on other objects on your table to change the material?

 

Try starting the table in the camera mode and crank the settings  way out to see if you can get a good look at what that blob is.

 

-Mike

[jimmyfingers]

I've seen random distortions and "objects" that appear from one launch to the next but it was intermittent and I took it to be a particular object that needed modifying / updating.  I didn't worry about it until I went around and cleaned up all items on the table I was working on and since I've got more updated the random "slices" don't appear any more.  I think it's related as before objects without materials used to be black and I would see it as a black slice through the screen.  I've seen it a couple times on a new table I'm trying to convert and the when it did it was pink. So seems to be some type of object corruption that can come and go from launch to launch.  Like I say, I didn't worry until I addressed all items on the table to try and narrow it down and I'm also not sure if you can be certain you "got it" until a total relaunch of VP and the table.

[toxie]

Alright great info on the AA ... with all antialiasing off, I get 190fps smooth. With nvidia enabled fxaa on I get 110fps smooth. This is much better. And a sweet new bloom effect....

 

Yup, as mentioned earlier, the VP/builtin FXAA and bloom don't work together yet.. :/

(the NVIDIA control panel one is okay though)

Edited by toxie, 12 February 2015 - 06:38 PM.

[cyberpez]

Thanks Unclewilly that did the trick!! I had set to to dark grey but not black.

 

I had only tried the table on my laptop, but tried it here at work (shhhhhh)  and the blob was still present when enabling opacity.  So not the video card like I thought.  I tried out the camera mode, thats a cool feature.  The blob was not present in it though.  The playfield was black, is that normal?  I did find a few objects I had not added materials to yet though.  I'll convert those and see what happens.  I also tried it in fullscreen mode and the blob was there, but not rotated, seemed to be the same size and shape.

 

I'll mess with it more tonight, thanks for your help guys.

[kiwi]

I've seen random distortions and "objects" that appear from one launch to the next but it was intermittent and I took it to be a particular object that needed modifying / updating.  I didn't worry about it until I went around and cleaned up all items on the table I was working on and since I've got more updated the random "slices" don't appear any more.  I think it's related as before objects without materials used to be black and I would see it as a black slice through the screen.  I've seen it a couple times on a new table I'm trying to convert and the when it did it was pink. So seems to be some type of object corruption that can come and go from launch to launch.  Like I say, I didn't worry until I addressed all items on the table to try and narrow it down and I'm also not sure if you can be certain you "got it" until a total relaunch of VP and the table.

I saw the same distortions, I seem to remember that I had to have two tables open at the same time.

 
I noticed that missing the session "Axis Scale" in primitive panel, as in VP9, this is a work in progress?

 

Thanks

 

Max