4027 replies to this topic

[wiesshund]

 

Do me favor and stop giving such wrong hints or information if you don't know the details how things work. If you want to build a table with VPX chose a version and build it with that version. But don't expect that this table will be playable with previous versions of vpx. This goes for all VP versions. If you want to test 10.7 than build a table with it but don't release it or play it for 10.6 or even 10.5. If it works it's more a coincidence than a feature.

 

It would help if you did not tell me not to do what i did not even say.
All i did was tell him how to get his table back so he could then work on it in VPX 10.6 again
 

[batch]

Ok, Fuzzel

 

It's just I'm a bit confused with these new developments

 

So, I go back to VP10.6 for tables I'll work on

[fuzzel]

 Do me favor and stop giving such wrong hints or information if you don't know the details how things work. If you want to build a table with VPX chose a version and build it with that version. But don't expect that this table will be playable with previous versions of vpx. This goes for all VP versions. If you want to test 10.7 than build a table with it but don't release it or play it for 10.6 or even 10.5. If it works it's more a coincidence than a feature.
 

It would help if you did not tell me not to do what i did not even say.
All i did was tell him how to get his table back so he could then work on it in VPX 10.6 again
 

I read your message in the way that you suggest to still use 10.7 for editing and use 4356 to switch between 10.6 and 10.7. Batch has seemed to manage to convert his table back to 10.6.

[fuzzel]

Ok, Fuzzel
 
It's just I'm a bit confused with these new developments
 
So, I go back to VP10.6 for tables I'll work on

The development hasn't changed. It was always this way. New versions are backward compatible but not in that way that you can use a table built with a newer version and play it in older versions without issues.

[wiesshund]

 

 

 Do me favor and stop giving such wrong hints or information if you don't know the details how things work. If you want to build a table with VPX chose a version and build it with that version. But don't expect that this table will be playable with previous versions of vpx. This goes for all VP versions. If you want to test 10.7 than build a table with it but don't release it or play it for 10.6 or even 10.5. If it works it's more a coincidence than a feature.
 

It would help if you did not tell me not to do what i did not even say.
All i did was tell him how to get his table back so he could then work on it in VPX 10.6 again
 

I read your message in the way that you suggest to still use 10.7 for editing and use 4356 to switch between 10.6 and 10.7. Batch has seemed to manage to convert his table back to 10.6.

 

 

No, i only suggest him to use that one to get it back to where it can be built in 10.6 again

there are things in the last version of 10.7 that do not exist in 10.6 at all, like the elasticity falloff for walls etc

[toxie]

Can't we all just get along?  

 

As for the various comments on sound and music issues: Thanks a lot for the reports! I hope i will finally be able to revisit this now over the holiday season.. So please bare with me some more..

 

As for 10.6 vs 10.7 compatibility: I fear the main issue this time is that the 10.7 cycle is simply going on for faaaaaar too long, compared to previous releases, but hopefully we can finalize the release soonish, so that everybody can just work with 10.7.

[toxie]

And for the VP10.7 version here is what I can read in the "Table Info"

 

 

And when I close the table, I can see this message at the top of the screen

 

It seems it adds the date and the hour I took the snapshot

This is a new feature. With some table authors and/or MODs it is difficult to distinguish versions, as the table info is simply not updated and naming schemes weird, so i thought its a good idea to also track internal revisions (i.e. each time its saved).

[batch]

Fuzzel & Toxie

 

My apologies if I wrote non appropriate information in this topic, I know you spend a lot of time to develop this fantastic tool

 

Merry Christmas, hoping new year will be more "Happy" than 2020

Edited by batch, 22 December 2020 - 10:02 PM.

[toxie]

the call stack looks like you tried to put a very long name and/or with wrong characters to a bumper. Element names shouldn't be longer than 32 characters.

..which is still super weird though, cause this case should be catched in the code (i.e. not crashing at least)..

@batch, do you remember what the name of that bumper was??

[wiesshund]

Can't we all just get along?  

 

We haven't stabbed each other yet

 

 

This is a new feature. With some table authors and/or MODs it is difficult to distinguish versions, as the table info is simply not updated and naming schemes weird, so i thought its a good idea to also track internal revisions (i.e. each time its saved).

 

 

I like that feature, as sometimes the author puts nothing in the table info, or the script, or even the table name
and so you kind of have no idea

[batch]

@batch, do you remember what the name of that bumper was??

 

Where can I find this information ?

 

Just Bumper1 & Bumper2 in the script

 

As I converted this table from VP9, perhaps the crash was before I replaced VP9 bumpers by VP10 ones, I can't remember ?

[Segovia11]

Dear Developers,

                            when you place a curser into the Elements properties name box and then select the element it adds 001 to the name. When you do the same again it will add another 001 to the name (which now resembles this number 001001).

Many thanks for spending time with this bug report

Joseph Gofton  

Edited by Segovia11, 24 December 2020 - 12:42 AM.

[jpsalas]

Dear Developers,

                            when you place a curser into the Elements properties name box and then select the element it adds 001 to the name. When you do the same again it will add another 001 to the name (which now resembles this number 001001).

Many thanks for spending time with this bug report

Joseph Gofton  

 

Yes, that's what happened I was going to report this bug, but I wasn't sure what I did that added that 001 to the name  

[hitman2304]

Are you already working on VPX using new graphic libraries like DX11 / 12 or Vulkan? I think it's time to think about the transition to a full-fledged 3d engine using full capabilities of modern graphics cards.

Edited by hitman2304, 24 December 2020 - 11:42 AM.

[fuzzel]

Are you already working on VPX using new graphic libraries like DX11 / 12 or Vulkan? I think it's time to think about the transition to a full-fledged 3d engine using full capabilities of modern graphics cards.

The current engine is already a full-fledged 3d engine. The only downside is that VPX is still using a static render pass. This static rendering is on the one side good for low/mid range systems on the other side it blocks other dynamic features.
And to answer your question: we're not working on such updates at the moment

[LynnInDenver]

Are you already working on VPX using new graphic libraries like DX11 / 12 or Vulkan? I think it's time to think about the transition to a full-fledged 3d engine using full capabilities of modern graphics cards.

You might want to watch the Visual Pinball Engine project, which is working on implementing features of Visual Pinball in Unity.

[hitman2304]

I am observing VPE thread and github page from very beginning, i think it's a very good and forward looking project

[Thalamus]

I'm just curious to VPE's performance. There is a reason for this pre-rendering in VP.

[hitman2304]

Played Shaderbytes Unity tables on Helios 2019 with i7 and gtx 1660 ti and i was getting about 150 fps in max settings. Graphics was way superior to VPX.

[Segovia11]

Dear Development Team,

                                          when "force exclusive Full Screen Mode" in Video/Graphics Options is selected you lose the mouse icon during game play. Which makes it more challenging for the user when "Enabled Mouse Handling during Play" is selected in Keys,Nudge and DOF.  (You can show the location of the pointer if you select "show location of pointer when I press the CTRL Key" in windows control panel / device and printers / mouse properties. which may take the frustration away!) 

 

Thank You Devs 

Happy coding and Enjoy

Joseph Gofton   

 

. .   

 |   

V

Edited by Segovia11, 24 December 2020 - 04:53 PM.