Shockman
appropriate at this time
- Joined
- Oct 26, 2004
- Messages
- 3,199
- Solutions
- 5
- Reaction score
- 121
- Points
- 90
- Favorite Pinball Machine
- Star Trek
Having acquired VS.net 2008 and having previous knowledge of C++ programming, and some Windows programming, along with a couple months of looking at the VP source code. I think it would be simple enough to make a couple of derivatives of VP. One, a VP9 version (not to be called VP9) with all those features it has, that is build to run all VP8 tables with the settings they were built with. This version would not be compatible with existing cabinets. Actually they would just be as out of whack as VP8 desktop versions are with existing new VP builds. Another build would be a dual purpose build, also with a new name that is for the building of new tables. and running of existing VP9 versions. So actually a VP9. This dual version will start as simply as pretty much a rebuild of VP9 with full support back for desktop users, namely startshake will be in the program and activated on demand, but default to on, and automatically go off if the table is rotated a full 90 or 270. One feature demanding it, Just one, to pop up, which I don't foresee, but can imagine, and this dual purpose version may or may not any longer exist, but separate versions for portrait and landscape surly will.
In other words with a VP9 based version, dropping cabinet building in favor of full backward compatibility, and another version, VP9 based, Dropping all pretenses of backward compatibility, in favor of endless possibilities, Could surly be in the cards, as far as my efforts.
Don't answer this unless and until I release a build of VP that has
-a nice plunger (graphically)
-a shiny ball
-VISUAL FEEDBACK TO NUDGING What a concept!, I know! I think it will catch on though. It will after all be a smart feature, knowing when to work and when not in or at least soon after the first release.
-A different layout for Table1.
I am working on a solution for making VP. And have many ideas including
-6 custom table templates, plus Standard(4/3 on 4/3), Widescreen(4/3 on 16/9), Rotated (4/3 on 16/9), Rotated (16/9 on 16/9) and maybe rotated (4/3 on 4/3).
-Startshake both scriptable, and hooked into the rotation function.
-much more. A new improvement or feature a week I would think.
If this becomes as comfortable, as any other programming environment I have committed myself to, I would expect in the not too distant future,
-Upgrade of DX.
-A new controller system.
-A new Graphics system, with nothing short of PNG and Alpha transparency.
-New physics like spin, ball weight, ball size.
-Grouping elements of objects.
-In other words anything and everything that I either know, or can learn.
I am going to Idaho for a few weeks in a few days. There is still prep. and setting up I need to get a VP making solution. I have to find the DX7.0 SDK and set it up. Learn the compiling process of VS.net and hopefully that's it. I will try to get a version out before I leave (about 8 days) and the offer will come the day I have figured out how to make it. So maybe sooner than that, maybe later.
It will not be much of course, and I have done so much to the source code of VP without a making solution already, that I suspect I will have to start over with a fresh source. Most of what I have done that I could not test, if you can believe it, is for the cabinet building aspect of it. Trying to get the scaling and offset on the same plane, and redesigning the flippers for a deeper, more overhead look to swing on the table instead of trying to dig through it. At that is surly whack. I also looked into drawing the display to reflect the changes of the rotated and scaled table, that I know is going to create problems.
Suggestions and requests are pointless, because I am not going to make you think that all you need to do is suggest something and I would be willing, or able to do it. Maybe year after next.
In other words with a VP9 based version, dropping cabinet building in favor of full backward compatibility, and another version, VP9 based, Dropping all pretenses of backward compatibility, in favor of endless possibilities, Could surly be in the cards, as far as my efforts.
Don't answer this unless and until I release a build of VP that has
-a nice plunger (graphically)
-a shiny ball
-VISUAL FEEDBACK TO NUDGING What a concept!, I know! I think it will catch on though. It will after all be a smart feature, knowing when to work and when not in or at least soon after the first release.
-A different layout for Table1.
I am working on a solution for making VP. And have many ideas including
-6 custom table templates, plus Standard(4/3 on 4/3), Widescreen(4/3 on 16/9), Rotated (4/3 on 16/9), Rotated (16/9 on 16/9) and maybe rotated (4/3 on 4/3).
-Startshake both scriptable, and hooked into the rotation function.
-much more. A new improvement or feature a week I would think.
If this becomes as comfortable, as any other programming environment I have committed myself to, I would expect in the not too distant future,
-Upgrade of DX.
-A new controller system.
-A new Graphics system, with nothing short of PNG and Alpha transparency.
-New physics like spin, ball weight, ball size.
-Grouping elements of objects.
-In other words anything and everything that I either know, or can learn.
I am going to Idaho for a few weeks in a few days. There is still prep. and setting up I need to get a VP making solution. I have to find the DX7.0 SDK and set it up. Learn the compiling process of VS.net and hopefully that's it. I will try to get a version out before I leave (about 8 days) and the offer will come the day I have figured out how to make it. So maybe sooner than that, maybe later.
It will not be much of course, and I have done so much to the source code of VP without a making solution already, that I suspect I will have to start over with a fresh source. Most of what I have done that I could not test, if you can believe it, is for the cabinet building aspect of it. Trying to get the scaling and offset on the same plane, and redesigning the flippers for a deeper, more overhead look to swing on the table instead of trying to dig through it. At that is surly whack. I also looked into drawing the display to reflect the changes of the rotated and scaled table, that I know is going to create problems.
Suggestions and requests are pointless, because I am not going to make you think that all you need to do is suggest something and I would be willing, or able to do it. Maybe year after next.
Last edited: