Jump to content



Photo
- - - - -

Star Wars: DSA Galactic Edition 1.5 playfield graphics missing


  • Please log in to reply
7 replies to this topic

#1 tprozac

tprozac

    Neophyte

  • Members
  • Pip
  • 6 posts

  • Flag: United States of America

  • Favorite Pinball: High Speed

Posted 31 December 2023 - 02:05 AM

Hi all. Trying to get DSA up and running on a Baller Installer 64 with DOF64 running. Everything is working after a few fresh re-imagings except the playfield graphics are not showing up. The animations and everything else is working including DOF.

PUP pack copied over. Terry’s instructions state to run a BAT in the pup-pack folder, I can not find a BAT.

Any help greatly appreciated. 4 days of futzing with this table to get here. So close. lol. At least VPX is running well.

Trev


Sent from my iPhone using Tapatalk

#2 TerryRed

TerryRed

    Pinball Fan

  • Silver Supporter
  • 1,823 posts

  • Flag: Canada

  • Favorite Pinball: Too many to choose...

Contributor

Posted 31 December 2023 - 03:20 AM

Hi all. Trying to get DSA up and running on a Baller Installer 64 with DOF64 running. Everything is working after a few fresh re-imagings except the playfield graphics are not showing up. The animations and everything else is working including DOF.

PUP pack copied over. Terry’s instructions state to run a BAT in the pup-pack folder, I can not find a BAT.

Any help greatly appreciated. 4 days of futzing with this table to get here. So close. lol. At least VPX is running well.

Trev


Sent from my iPhone using Tapatalk

 

 

The Option xx.BAT files are in each PinEvent table's PuP-Pack folder. If you have windows set to hide file extensions, you won't see the .bat part of the filename. Run the Option xx.bat that matches the setup your are using. That's it. This is only setting up the pup-pack, nothing else.

 

As for playfield graphics missing... be sure you are using the "required" FP video settings (I included these in the table's zip). Be sure you are completely closing FP everytime you exit a table before reloading the same table or another table. FP needs to start clean each time a table is run. If you see anything corrupt / missing, just close FP completely and try again. As long as your GPU has a good amount of VRAM (and your PC has 8 GB ram or more), you should have no problems running the table.

 

If you haven't done so... install my newest FP and BAM Essentials AIO, which has my latest guides, "Start FP" bat files, and is always up to date, It can be very helpful.

 

https://www.vpforums...showtopic=51600


Edited by TerryRed, 31 December 2023 - 03:32 AM.


#3 tprozac

tprozac

    Neophyte

  • Members
  • Pip
  • 6 posts

  • Flag: United States of America

  • Favorite Pinball: High Speed

Posted 31 December 2023 - 08:00 AM

Terry,

First of all, Thank you for taking the time to help me out. Your tables Tron and SW DSA are the inspiration for me to build my cab. Thanks a lot ;-) Actually an amazing hobby and your tables are so next level I am so thankful to get to play them!

1. Found the Option BATs. Thanks, was being a bit blind, apologies. Selected Option 1 and executed the BAT. It is confirmed in a txt file that "Option 1" is the selected option. Note that the PuP-Pack folder is in: C:\vPinball\PinUPSystem\PUPVideos.
- I hope that is the right place?
- Is there anything else I need to do that I might have missed? I did install with latest Baller Installer.

2. Playfield Graphics.
a. Have double checked the "required" FP video settings. They conform to Multiscreen Setups (PinEvent tables with PuP-Packs):
image.png

b. I have completely closed all applications and rebooted in between attempts, but no luck so far.
c. Video Card: Radeon 6600 8GB VRAM
d. Installed: FP and BAM Essentials AIO (Latest Version) & Ran Start FP - PinEvent PuP-Pack DMDExe.bat

No luck so far. Still no playfield graphics. Here are a parsed version of the DirectOutput.log. It seems that DOF can not find the TableFilename:

DirectOutput Version 3.1.7776.42172, built 2021.04.16 23:25
MJR Grander Unified DOF R3++ edition feat. Djrobx, Rambo3, and Freezy
DOF created by SwissLizard | https://github.com/mjrgh/DirectOutput
2023.12.30 22:44:55.776 DirectOutput Logger initialized
2023.12.30 22:44:55.564 Global config filename is "C:\DirectOutput\config\GlobalConfig_B2SServer.xml"
2023.12.30 22:44:55.776 Global config loaded from: C:\DirectOutput\config\GlobalConfig_B2SServer.xml
2023.12.30 22:44:55.776 Loading Pinball parts
2023.12.30 22:44:55.776 Loading cabinet
2023.12.30 22:44:55.778 Will load cabinet config file: C:\DirectOutput\Config\cabinet.xml
2023.12.30 22:44:56.171 1 output controller defnitions and 4 toy definitions loaded from cabinet config.
2023.12.30 22:44:56.171 Cabinet config file has AutoConfig feature enabled. Calling AutoConfig.
2023.12.30 22:44:56.171 Cabinet auto configuration started
2023.12.30 22:44:56.284 PhilipsHueAutoConfigurator.AutoConfig started...note, actual connection detection will happen asynchronously, and device disabled if not succesfull (check further down in the log)
2023.12.30 22:44:56.293 LedWiz-like device at VID=1118, PID=1957, product string=Microsoft 2.4GHz Transceiver v9.0, manufacturer string=Microsoft
2023.12.30 22:44:56.300 LedWiz-like device at VID=1118, PID=1957, product string=Microsoft 2.4GHz Transceiver v9.0, manufacturer string=Microsoft
2023.12.30 22:44:56.306 LedWiz-like device at VID=4660, PID=273, product string=VirtuaPin Controller, manufacturer string=
2023.12.30 22:44:56.315 LedWiz-like device at VID=2821, PID=6457, product string=AURA LED Controller, manufacturer string=AsusTek Computer Inc.
2023.12.30 22:44:56.322 LedWiz-like device at VID=1118, PID=1957, product string=Microsoft 2.4GHz Transceiver v9.0, manufacturer string=Microsoft
2023.12.30 22:44:56.329 LedWiz-like device at VID=1118, PID=1957, product string=Microsoft 2.4GHz Transceiver v9.0, manufacturer string=Microsoft
2023.12.30 22:44:56.334 Cabinet auto configuration finished
2023.12.30 22:44:56.334 Autoconfig complete.
2023.12.30 22:44:56.334 Cabinet config loaded successfully from C:\DirectOutput\Config\cabinet.xml
2023.12.30 22:44:56.334 Cabinet loaded
2023.12.30 22:44:56.334 Loading table config
2023.12.30 22:44:56.334 No TableFilename specified, will use empty tableconfig
2023.12.30 22:44:56.334 Will try to load configs from DirectOutput.ini or LedControl.ini file(s) for RomName FP_PE_SW_DSA_GE
2023.12.30 22:44:56.335 Loading LedControl file C:\DirectOutput\directoutputconfig30.ini
2023.12.30 22:44:56.352 Min DOF Version is 0.8 for file directoutputconfig30.ini
2023.12.30 22:44:56.352 Resolving Tables Variables
2023.12.30 22:44:56.353 Resolving Global Variables
2023.12.30 22:44:57.937 1 directoutputconfig.ini or ledcontrol.ini files loaded.
2023.12.30 22:44:57.938 Config for RomName FP_PE_SW_DSA_GE exists in LedControl data. Updating cabinet and config.

I just tried Retroflair and same issue. I must have fat fingered a setting somewhere….

Any help would be greatly appreciated!

Best,

Trev2789f0364cca291993db46dc0d59f35e.jpg


Sent from my iPhone using Tapatalk

Edited by tprozac, 31 December 2023 - 08:10 AM.


#4 tprozac

tprozac

    Neophyte

  • Members
  • Pip
  • 6 posts

  • Flag: United States of America

  • Favorite Pinball: High Speed

Posted 31 December 2023 - 09:36 AM

Found issue. Latest AMD Radeon Adrenaline Drivers have an issue rendering Playfield. Stock Windows driver corrected the issue and Playfield has now reappeared on all Future Pinball tables.

Now I need to try to confirm PuP-Packs and Pin-event v2 are working.

Thanks Again Terry!

Trev


Sent from my iPhone using Tapatalk

#5 TerryRed

TerryRed

    Pinball Fan

  • Silver Supporter
  • 1,823 posts

  • Flag: Canada

  • Favorite Pinball: Too many to choose...

Contributor

Posted 31 December 2023 - 10:24 AM

Found issue. Latest AMD Radeon Adrenaline Drivers have an issue rendering Playfield. Stock Windows driver corrected the issue and Playfield has now reappeared on all Future Pinball tables.

Now I need to try to confirm PuP-Packs and Pin-event v2 are working.

Thanks Again Terry!

Trev


Sent from my iPhone using Tapatalk

 

It's sad to say, but as soon as I saw AMD / Radeon.... I assumed it was an AMD driver issue. Not uncommon.

 

Regarding DOF.... nothing to do on the FP PinEvent side as long as you have it enabled in PinEvent_V2_Settings.txt for the mode you play in.

 

Just be sure the BAM iCOM plug-in is enabled and not set to Paranoid (off).

 

 

Make sure you have the latest 32 bit DOF update. (I think R3++ is still the lates... get that at mjr's site).

 

If you have DOFLinx installed and running, make sure its not running when launching a PinEvent table, as it will interfere will the table's DOF.

 

 

All this is covered in my PinEvent V2 Guide and my FAQ and Help Guide.


Edited by TerryRed, 01 January 2024 - 09:54 AM.


#6 tprozac

tprozac

    Neophyte

  • Members
  • Pip
  • 6 posts

  • Flag: United States of America

  • Favorite Pinball: High Speed

Posted 07 January 2024 - 12:34 AM

Attract mode crashes at random after 5 min or so with random unknown memory errors quoted in log. I am afraid it is an AMD issue again. Anyone experience this? I am Waiting for the 4080 super to come out before buying an nVidia to see if that helps. Costly bug fix :-).

Am running in Windows 8 compatible mode and did reinstall 2 in 1 installer fresh

Sent from my iPhone using Tapatalk

Edited by tprozac, 07 January 2024 - 12:49 AM.


#7 TerryRed

TerryRed

    Pinball Fan

  • Silver Supporter
  • 1,823 posts

  • Flag: Canada

  • Favorite Pinball: Too many to choose...

Contributor

Posted 07 January 2024 - 06:13 AM

Attract mode crashes at random after 5 min or so with random unknown memory errors quoted in log. I am afraid it is an AMD issue again. Anyone experience this? I am Waiting for the 4080 super to come out before buying an nVidia to see if that helps. Costly bug fix :-).

Am running in Windows 8 compatible mode and did reinstall 2 in 1 installer fresh

Sent from my iPhone using Tapatalk

 

 

Don't ruin in Windows 8 Compatibility mode at all (FP runs with worse fps in this mode). That used to be a fix for crashing a long time ago, but newer BAM updates and Windows updates fixed that issue. Make sure your Windows and drivers are all up to date, and make sure Defender and other Anti-Virus are not active.


Edited by TerryRed, 07 January 2024 - 06:14 AM.


#8 tprozac

tprozac

    Neophyte

  • Members
  • Pip
  • 6 posts

  • Flag: United States of America

  • Favorite Pinball: High Speed

Posted 10 March 2024 - 11:24 PM

Hey there Terry! Hope you are having a great Sunday. Just installed a brand new 4080 super. Getting wierd boots. Playfield disappears load screen on DMD see pics. Any thoughts?5775a8dbca3465952161d6ede93b8bf3.jpg
c2966de2fcbfb060f3f68506f46ae9b8.jpg


Sent from my iPhone using Tapatalk