4027 replies to this topic

[evilantal]

I'm getting extremely long loading times with the latest version.

Also, when I want to exit a table via ESC > Q, the directB2s quits, but the playfield image is frozen and I can only quit VP by using the task manager. Is that only me?

[Thalamus]

I just did a re-test for that already mentioned sword of fury, and the issue is still there, but, this time the rom sounds was also very low. Going back to 10.6, and everything was fine again.

[George Corrigan]

I found a bug 10.6 and would assume it still exists in 10.7. I'm not sure if this is where I should report it, so my apologizes if this is not.

 

I discovered if have an object with a 32 characters long name, it will corrupt that object. If you click to select that object, Visual Pinball crashes. So that object cannot be selected, modified, or deleted.

 

If you would like to replicate this. Create a blank table. Add an object (target and ramp were tested), change the name to something that is 32 characters long. Close and reopen the table. Select the object with the long name and visual pinball will crash.

[fuzzel]

rev4090 is up:

 

- add WEBP to list of supported image formats
- revert rev 4001 (only handle contacts that happened in the current hittime window), as it leads to missed intersections in (at least) CCC (Saloon) and MM NZ&TT Reloaded Skitso (bumper area)
- output error code on table load failure
- mark table also as dirty/needs-to-be-saved when only deleting text in the script
- fix top material property handling of walls
- restore pre-VPX10.4 behavior for sounds that were re-routed to the backglass via their name/path, also make by default all the other sounds to be routed to the table for VP8/9 tables

 

[LynnInDenver]

Is there a "mark table as dirty/needs-to-be-saved" when you load POVs or run F6 Camera Mode? I haven't looked lately using 10.6, but I've gotten in the complete habit of hitting save when I come out of Camera Mode to compensate for an earlier/present lack.

[Malcom]

I'm getting extremely long loading times with the latest version.

Also, when I want to exit a table via ESC > Q, the directB2s quits, but the playfield image is frozen and I can only quit VP by using the task manager. Is that only me?

Hi,

I have the same issue when i want to quit a table with ESC and Q.

[Slydog43]

 

I'm getting extremely long loading times with the latest version.

Also, when I want to exit a table via ESC > Q, the directB2s quits, but the playfield image is frozen and I can only quit VP by using the task manager. Is that only me?

Hi,

I have the same issue when i want to quit a table with ESC and Q.

 

 

I have that issue only when I turn on force-Exclusive, goes away when I turn off.

[fuzzel]

What is ment with long loading times? Loading time of the VPX editor, loading time of the table or loading time when you start the game?

 

I can confirm that there is a problem with exclusive fullscreen when you quit the player. But I don't have a clue why that happens...

Edited by fuzzel, 11 May 2020 - 06:51 PM.

[Malcom]

What is ment with long loading times? Loading time of the VPX editor, loading time of the table or loading time when you start the game?

 

I can confirm that there is a problem with exclusive fullscreen when you quit the player. But I don't have a clue why that happens...

Hi Fuzzel,

 

The issue with the exclusive fullscreen appeared since rev4090 for me, i tested all your previous rev.

[fuzzel]

Ah thanks for the hint. Will be fixed in the next version. What about the loading times?

[davidcd13]

I have the same problem with the loading time of the application, but it is quite random. Sometimes I launch the application, I see that the mouse icon displays the loading but the application does not launch. I have to restart the application, then it loads.

I tried launching with PinballX and I find the same problem, sometimes the table starts instantly, sometimes it is extremely long, sometimes the table does not start.

But most of the time the application launches instantly.

Edited by davidcd13, 12 May 2020 - 03:59 PM.

[Slydog43]

I have found loading times to be equal or better on my cabs

[Rajo Joey]

I just test it on my PC, only loading the program. There is no difference between v10.6 and v10.7. Both programs open in 1 to 2 seconds.

[jejepinball]

Hi, just an annoying thing : the properties panel of a component no longer displays the type (bumper, trigger...) of the component !

Thank You for your work, it's great.

[fuzzel]

Hi, just an annoying thing : the properties panel of a component no longer displays the type (bumper, trigger...) of the component !
Thank You for your work, it's great.

Yes that's a known issue. I will add that.

[CARLOSGUIZZO]

 

I have the same problem with the loading time of the application, but it is quite random. Sometimes I launch the application, I see that the mouse icon displays the loading but the application does not launch. I have to restart the application, then it loads.

I tried launching with PinballX and I find the same problem, sometimes the table starts instantly, sometimes it is extremely long, sometimes the table does not start.

But most of the time the application launches instantly.

 

Same here

[Slydog43]

I have now seen the long loading times.  I was confused, its not the table loading times, its loading of VP itself.  I dblclicked on VPX icon and I thought nothing happened.  After about 20-30 seconds VPX did load up.  Very strange.  This doesn't seem to happen very often though.

[fuzzel]

Yes I have this too from time to time. Very strange. Maybe something is wrong with the event handling while starting VP.

[toxie]

Is this for all of you about the loading of the (empty) program or only when loading a table?

[studlygoorite]

I don't know if this is doable and don't laugh but I find that when going into a table's sound manager (with 10.6) and bumping the volume on a specific sound from 0.0 to the max 1.0 the results are minimal. Quite often I find I have to use software like Audacity to amplify the sound and re-import. Is it possible to implement a change to the volume adjuster to make it more responsive?