8 replies to this topic

[epthegeek]

I played around with it a while and it doesn't seem like there is a way - but I figured I'd ask just in case.

Ever since VP started using layback to get a keystone affect, the squared out 'arcade' view on FP looks terrible to me.

Playing around with the manual camera, I've found that I really prefer this style of view for FP on my cabinet:

 fpbk2k.jpg   747.67KB   116 downloads

But I can only get there with the manual camera, which I can't seem to save

Unrelated, but for some reason the 'hud' toggle key doesn't seem to work for me anymore. Even if I change it, so that's why it's still on in the picture.

[thewool]

I just wanted to bump this thread for the exact same reason. You can achieve a pretty good keystone view in FP but it won't save. Does anyone know of a workaround for this?

Cheers.

[JonBaker]

The manual view cannot be saved, no. And certain keystrokes (like the HUD key) will not work in manual view.

[thewool]

Although the camera position can't be saved.... I read a old post on a forum where someone suggested this could be achieved with a script using 'Auto it'. I installed it and had a quick play but couldn;t get it to work properly. The full post is below.

Maybe something could be done with Auto Hot Key script, this could then be launched from hyperpin somehow... Any AHK wizzes on here fancy helping out?

------------------------------------------

Didouc2 from over at FP Forums has come up with a brilliant idea for those of you who have made a physical pinball table for use with Future Pinball. Didouc2 has written an example script to enable you to start up a Future Pinball table using a particular camera angle by default, this is ideal for those of you using a "lay down" screen on your pinball tables.The script is written using Autoit (Freeware) and needs to be modified for each table you wish to run

See script below for an example, naturally you will need to modify the path to your table within the script:

;On lance future pinball + la table
Run ('c:\progra~1\future~1\future~1.exe /open "c:\progra~1\future~1\tables\Sci-Fi~1.fpt" /play /Exit')
WinWaitActive ( "Future Pinball - © 2007 BSP Software Design Solutions" )
sleep(10000)
;change view to Top view
Send("{F8 2}")
; change view to manual camera
Send("{F11}")
;zoom in while x msec
Opt("SendKeyDownDelay", 620)
Send("z")
sleep(500)
;zoom out while x msec
opt("SendKeyDownDelay", 500)
Send("s")
; stop manual camera
MouseClick("right")
Exit

[natural320]

oh I'll resurrect this...~bumpity~

anyone get the above or any other method to work? I've been spoiled a bit by VP, but I am digging some of the tremendous FP tables at the moment (HE-MAN FTW!!!)

[Steve Paradis]

I made a script with AutohotKey which
Launch any table, adjust the camera angle
and close FP completely on escape.

First download the free AutoHotKey from http://www.autohotkey.com/
then in a .txt file paste the following code and name it whatever you want as long as it have the .ahk extension

***************************************
Code:#SingleInstance force ; MAKE SURE THIS SCRIPT DOESN'T RUN TWICE AT A TIME
FileRead, Contents, path.txt ; GET THE VARIABLE FROM THE PATH.TXT FILE
Run, C:\Games\FuturePinball\FPPhysics24A.exe /open %Contents% /play /Exit,
WinWait, ahk_class FuturePinballOpenGL ; WAIT FOR FP TABLE TO OPEN
IfWinNotActive, ahk_class FuturePinballOpenGL, ; LOOP UNTIL THE TABLE IS FULLY LAUNCHED
WinWaitActive, ahk_class FuturePinballOpenGL, ; WHEN TABLE IS LAUNCHED GIVE IT FOCUS

Sleep 9000 ; PAUSE THE SCRIPT TO SKIP THE ANNOYING TABLE OPENING TRANSITION
Send {f8} ; SELECT THE APRON VIEW
Sleep 1000 ; WAIT UNTIL THE TRANSITION IS MADE for 1 SEC
Send {f8} ; ...THEN SELECT TOP VIEW
Sleep 1000 ; WAIT A BIT AGAIN for 1 SEC...DAMN TRANSITION!
Send {f11} ; PUT FP IN MANUAL CAMERA MODE
Sleep 100 ; WAIT A BIT AGAIN for 0.1 SEC
Send {w down} ; HOLD ZOOM IN KEY
Sleep 800 ; WAIT A BIT AGAIN for 0.8 SEC
Send {w up} ; RELEASE ZOOM IN KEY
Sleep 100 ; WAIT A BIT AGAIN for 0.1 SEC
Send {Click right} ; DISENGAGE MANUAL CAMERA MODE
Sleep 100 ; WAIT A BIT AGAIN for 0.1 SEC
Send {Click up right} ; RELEASE RIGHT CLICK BUTTON
return


; SO IF YOU USE A PC WITH A DIFFERENT SPEED THAN MINE WHICH IS VERY LIKELY,
; I GUESS YOU WILL HAVE TO ADJUST THE TIMER PARAMETERS WHERE YOU SEE "SLEEP"



you will need a path.txt file also in the same folder containing the path of the table you want to launch, in my case :
Code:"C:\Games\FuturePinball\Tables\LightSequencerDemo.fpt"

Note1**Quotes mark are important to keep!!

Note2**in the end you can make your script an executable by rightclicking on it and select "compile script".

Now have fun..making your very own camera angle....

[chepas]

Alright Steve

Just wondering if you stuck with this method over using arcade render with the lighting angle working?

Added the script to FPLaunch and can get a good angle by catching the camera as it moves from apron to top view. With a little mouse move to the right to straighten her up a bit.

I'm not at a cab atm so I can't really determine if it's all that magical, but sitting in front of a rotated screen it's good.

Really not sure if it's ideal to have the inside walls of the table showing on a pincab but graphics & models seem so much better this way. Tried every angle in the render mode, even right down to 8a.

[jimhoyle]

For anyone who might use this. This is my Autohotkey script snippet. I'm using a vertical monitor, that probably affects the result. First you have to do F2 (if not defaulted to that), then press 5 and it'll fix the angle for you. If the result is weird, just change the numbers (check the code comments).

 

 

; ----- Future Pinball ------------------------------------------
#IfWinActive ahk_class FuturePinballOpenGL
  5::
  Send {F2} ; reset to F2 view
  Sleep 20 ; sleep for much longer here if you want to reset from all views
  Send {F11} ; go to F11 manual camera
  MouseClick, left
  MouseMove, 0, 50, 0, R ; (x, y, slowness, R=Relative)
  Sleep 100
  MouseMove, 0, 50, 0, R ; have to repeat like this..
  Sleep 100
  MouseMove, 0, 50, 0, R ; ..because slowness was random..
  Sleep 100
  MouseMove, 0, 50, 0, R ; ..and over 50 was nulled
  Sleep 100
  Send {s down} ; zooming out
  Sleep 1500
  Send {s up}
  Sleep 20
  MouseMove, 0, -50, 0, R
  Sleep 100
  MouseMove, 0, -50, 0, R
  Sleep 100
  MouseMove, 0, -50, 0, R
  Sleep 100
  MouseMove, 0, -5, 0, R
  Sleep 100
  Send {w down} ; zooming in
  Sleep 700
  Send {w up}
  Sleep 20

  MouseClick, right ; disengage manual camera
  return
#IfWinActive

[darquayle]

FPLaunch is so flexible.  I continue to find new ways to use this launch portion of Hyperpin.  I too have wanted to have multiple table views that are not part of the standard F2, F3, F4, etc. variety.  So, using the cues listed above, I added a section in my FPLaunch script that allows me to toggle through five distinct table views.  I've mapped my Alt-F10 and Alt-F11 keys to toggle forward and backward between these table views.  I don't have a PinCab but I use a Logitech wireless controller as my input device and I have two of my buttons mapped for these two keys.  It really works great for my usage as sometimes I have my monitor vertical and other times I have it flat (like a pincab).  Below is the code snippits that I use in my FPLaunch file.

 

 

ManCamBack:
Global Camera
Camera -= 1
If (Camera = 0) {
  Camera = 5
}
GoSub ManCam1
Return

ManCamForward:
Global Camera
Camera += 1
If (Camera = 6) {
  Camera = 1
}
GoSub ManCam1
Return


ManCam1:
Global Camera

If (Camera = 1) {
 Send {f2}
}
 Else if (Camera = 2) {
	Send {f2} ; SELECT THE APRON VIEW
	Sleep 500 ; WAIT UNTIL THE TRANSITION IS MADE for 1 SEC
	Send {f11} ; PUT FP IN MANUAL CAMERA MODE
	Sleep 100 ;  WAIT A BIT AGAIN for 0.1 SEC
	Send {w down} ; HOLD ZOOM IN KEY
	Sleep 500 ; WAIT A BIT AGAIN for 0.8 SEC
	Send {w up} ; RELEASE ZOOM IN KEY
	Sleep 100 ; WAIT A BIT AGAIN for 0.1 SEC
}
Else if (Camera = 3) {
	Send {f2} ; SELECT THE APRON VIEW
	Sleep 500 ; WAIT UNTIL THE TRANSITION IS MADE for 1 SEC
	Send {f11} ; PUT FP IN MANUAL CAMERA MODE
	Sleep 100 ;  WAIT A BIT AGAIN for 0.1 SEC
	MouseMove, 0, -40, 50, R ; have to repeat like this..
    Sleep 500
	Send {w down} ; HOLD ZOOM IN KEY
	Sleep 700 ; WAIT A BIT AGAIN for 0.8 SEC
	Send {w up} ; RELEASE ZOOM IN KEY
	MouseMove, 0, 45, 50, R ; have to repeat like this..
   Sleep 100
	Send {w down} ; HOLD ZOOM IN KEY
    Sleep 500
	Send {w up} ; RELEASE ZOOM IN KEY
    Sleep 500
}
Else if (Camera = 4) {
	Send {f2} ; SELECT THE APRON VIEW
	Sleep 500 ; WAIT UNTIL THE TRANSITION IS MADE for 1 SEC
	Send {f11} ; PUT FP IN MANUAL CAMERA MODE
	Sleep 100 ;  WAIT A BIT AGAIN for 0.1 SEC
	MouseMove, 0, -30, 50, R ; have to repeat like this..
    Sleep 500
	Send {w down} ; HOLD ZOOM IN KEY
	Sleep 700 ; WAIT A BIT AGAIN for 0.8 SEC
	Send {w up} ; RELEASE ZOOM IN KEY
	MouseMove, 0, 35, 50, R ; have to repeat like this..
   Sleep 100
	Send {w down} ; HOLD ZOOM IN KEY
    Sleep 400
	Send {w up} ; RELEASE ZOOM IN KEY
    Sleep 500
}
 Else if (Camera = 5) {
	Send {f2} ; SELECT THE APRON VIEW
	Sleep 500 ; WAIT UNTIL THE TRANSITION IS MADE for 1 SEC
	Send {f8} ; SELECT THE APRON VIEW
	Sleep 1000 ; WAIT UNTIL THE TRANSITION IS MADE for 1 SEC
	Send {f8} ; ...THEN SELECT TOP VIEW
	Sleep 1000 ; WAIT A BIT AGAIN for 1 SEC...DAMN TRANSITION!
	Send {f11} ; PUT FP IN MANUAL CAMERA MODE
	Sleep 100 ;  WAIT A BIT AGAIN for 0.1 SEC
	Send {w down} ; HOLD ZOOM IN KEY
	Sleep 1800 ; WAIT A BIT AGAIN for 0.8 SEC
	Send {w up} ; RELEASE ZOOM IN KEY
	Sleep 100 ; WAIT A BIT AGAIN for 0.1 SEC
	;Send {Click right} ; DISENGAGE MANUAL CAMERA MODE
	;Sleep 100 ; WAIT A BIT AGAIN for 0.1 SEC
}
Return

Towards the top of the script where the other keys are assigned (around line 300), I set the key preferences for the forward and back buttons:

camera = 1
mancamback      = !F10     ; Choose Previous Manual Camera
mancamforward   = !F11	  ; Choose Next Manual Camera

And around line 500 (where the other hotkeys are declared, I associate the key preferences to the code snippits.

	Hotkey, $%mancamforward%, ManCamForward
	Hotkey, $%mancamback%, ManCamBack

For me, this has worked great!  I can always tweak the code to add a 6th or 7th manual camera view, or I can reduce some of the less frequently used views.  As always, your mileage may vary, so if you use the code above, you may have to tweak some of the mouse and key delays based upon your own preferences.

 

Hope this provides some value.  I'm always learning from the forum members and hopefully I can give a tiny bit back.