RustyCardores

yes it's set to 32bit. The machine has been running fine for ages and I've just updated it with some new tables. Not all images are washed out though... just the newer ones. They have come direct from my other machine which was a sister build. It's my standard practice to update one machine and then just dupe the changes to the second. This form of updating has never been a problem before. I'm a photographer by profession and if this was a calibration issue in my workflow, I would think it was due to images saved in CMYK or AdobeRGB being forced to display in sRGB. Perhaps I should just drop all these images in photoshop where I can see if there are any profile conflicts going on? (Might even load Photoshop into the pinball cabinet, as it would come in handy from time to time)

I assumed they would effect only video? These are the .png screen grabs and I've never seen it happen on either of my two machines before.

I was updating the sister machine to mine yesterday and noticed that some of the new table images in the PBX menu are washed out. These are images that have come from my machine and display fine there. The game tables themselves look fine, so I grabbed new screen shots and replaced them in the PBX menu.... but these too look dull and washed out in the PBX menu. Any ideas? Cheers Rusty. Note: Latest PBX on Win7

Not sure if it's been mentioned.... but add Steam/PinballFX2 support to the "Other System" types. I'm a Win7/Steam user and PBX works a treat launching PinballFX2 under Steam, but there are some other Steam apps that I would like to launch directly as well.

A quick and dirty solution might be to create a new 'group' just with the one table in it. If you switch to that group each time you shut down, it should then reopen in that group and display the required table shouldn't it?

Yeah it's got me stuffed. Im doing a backup right about now

OK never mind I have it working now. Not the old way though. This time I simply put Kodi.exe to my 'Launch Before' and made the irfanview slideshow exe my 'system'. I have no idea why it works in this reverse way??? ..... but it works exactly as it did before and that's all that matters.

Ignoring the fact that this is Kodi etc... what would be your recommendations for simply launching an exe? I've not been able to get Kodi to run again, so I compiled a stand alone exe script that does all the launching and screen rotating etc.... sadly I cant get it to run either. I dunno how I managed to get this to work in the first place..... I must have been on the good stuff back then

Nope. have not touched it in months. The only things I have done (apart from adding more tables in the regular fashion) is that I have added an additional group setup to run SLAMT1LT's tables separately under their own menu. Plus I loaded Unit3D Pinball Beta..... I was only testing this and ran it as a stand alone, so did not make any adjustments to PBX for it in any way. (it does mod the vpinmame, but that shouldn't concern us here)

Sorry, I took the easy way. My network has been stupidly flakey here all day and I'm working on a combo of mobile phone and remote access to the pincab.

I've been muddling around try to make this work and I think I have confused myself enough to say that I have now forgotten where I started ....oh well, that log is where i'm currently at now.

https://dl.dropboxusercontent.com/u/8504136/Pinball/log.txt

After months of PBX successfully launching Kodi as my Juke Box on my cab, it has simply stopped working. I can execute Kodi.exe directly from the app folder and it works fine, so there is nothing wrong with Kodi itself. In PBX I have Kodi as an 'other system' and the paths to Kodi's folder & exe check out fine. (they have never changed and it ran for months remember) I have a 'launch before' for Irfanview to run a slide show for my main screen.... this is working fine. I have a 'launch after' for a BAT file to kill Irfanview.... this too is working fine. But... dawg namit, Kodi just doesn't execute and the process halts at the PBX loading screen (I can see that this screen is active behind, even though Irfanview has the focus) I have reset all paths, checked permissions on Kodi.exe, even updated to the latest PBX..... but I just cant get it to launch. Any ideas? ------------------------- [system_3]Name=KodiEnabled=TrueSystemType=0WorkingPath=C:\Program Files (x86)\KodiTablePath=C:\Program Files (x86)\KodiExecutable=Kodi.exeParameters=[TABLEFILE]LaunchBeforeEnabled=TrueLaunchBeforeWorkingPath=C:\PinballXX\Media\KodiLaunchBeforeExecutable=IrfanviewTableSLideshow.exeLaunchAfterEnabled=TrueLaunchAfterWorkingPath=C:\PinballXX\Media\KodiLaunchAfterExecutable=killirfanview.batLaunchBeforeWaitForExit=FalseLaunchBeforeHideWindow=FalseLaunchAfterWaitForExit=FalseLaunchAfterHideWindow=False

I'm trying to get PinballX to launch Project64 (Nintendo64 Emulator) The game & Project64 are working fine on their own. I have created another system within PinballX for Project64 and it successfully launches the app, but I just can't get the table/rom parameters right so that the game launches. I have tried everything I could find in the gameex forum, including using " and not using them etc, but no success. Has anybody here got Project64 working under pinballx and if so, what launch parameters are you using? Cheers, Rusty.

No Pinball FX splash screens? If so, that's something I need to investigate!

So far so good here. But it has been an intermittent issue to date so it's hard to be certain. .....plus I've not much time to play at the moment. That cruise ship I was telling you about departs tomorrow and I've so much to get done before I go.

With mine it seems to repair itself for a bit when attract mode starts, then it will go wacko again. I wonder if it's a particular wheel image that causes the problem? Could it be a dodgy header/exif issue? But if that was the case, it should happen if we do a slow scroll to view each wheel image shouldn't it? .... as apposed to it being random. (....well at least it appears to be random I think?)

Sorry Tom, But the off-centre wheel image issue hasn't disappeared after all Cheers Rusty

No, thank you for all your testing and thanks to the PBX team for all the effort that goes into what is a fantastic front end. My cabinet wouldn't be what it is without PBX. I look forward to making some new bits and pieces, but that will have to wait for a month, as I have a cruise ship waiting to take me to Hawaii. (geez I hope they have pinball on board!! lol)

Yup, that should be no problem. This is a pretty crappy sample (I spent all of about 5 seconds on it), but it will give people an idea of where we are headed... undelay1920_DARKFIRE_SHADED2_PHYSMOD.png.zip

A selection of Underlay Images to suit 1920x1080 Desktop Screens For those who have not followed the thread above, please understand PinballX contains a hard top limit as to where it positions the underlay image file on screen. In desktop mode, this limit presently sits too close to the height of the path that the wheel images follow. For this reason, these arches have been designed as a "baseline path" to follow, rather than a "background path". So when you see your table wheel images overhanging the top of the arch, that is intentional (and unavoidable with PinballX's present code). Cheers, Rusty -------------------------------------------------------------------------------- 1080 Pixel underlays for Cabinets can be downloaded HERE --------------------------------------------------------------------------------- . Underlay Images 1920 Desktop.zip

Yeah that lines up pretty good hey. I think we have our desktop underlay template at last. Thanks for all your effort testing these. I will make batch of colour versions now and post them shortly.

Actually that looks pretty good! The hard coding of the image top position is certainly the problem, as the top of the arch will always be in that same spot ....and sadly that spot is actually below the height of the wheel images. I think there might still be a little bit of squishing going on from PBX however, as the wheel images get a little higher above the arch as they go up. So that suggests to me that the arch is being pushed down and flattened. Here is another with an even thinner arch... let's see how that goes. (I will hazard a guess and say that we will prob need to be somewhere in the middle of the two) BOOMERANG_THINNER.zip