4027 replies to this topic

[wiesshund]

 

and for everybody without github login: https://github.com/v...7.0-127-c9c069f

@Toxie, I've always Used the 32bit executable and here is also the x64 version... so which one should I use ? I'm puzzled

 

 

The 64bit works, and actually seems maybe a bit more efficient.
But B2SServer is only 32bit, so you wont get any backglasses showing
(which also could be the reason it seemed a bit more efficient)

 

Still, was interesting to play with it some, 1st time i got to play with an up to date build of it.

[remdwaas1986]

lol, i used the 64 bits but did what wies said, just rename the exe to version 10.7 and leave everything else good, i played your table mephisto jp and i have no issues with sound or anything else. i keep building now tables in 10.6 till 10.7 fully is released because its backwards compatible. I liked your script with flex JP that saves me again uploading 2 tables. i modified the code of my sample table with it. And that without help 

[Thalamus]

I believe the major issue with going 64bit is that at91jit isn't working in pinmame64. So, you are kind of stuck on 32bit, because, like JP says. It is a all or nothing kind of thing. Just make efficient tables and that won't be an issue

[wiesshund]

I believe the major issue with going 64bit is that at91jit isn't working in pinmame64. So, you are kind of stuck on 32bit, because, like JP says. It is a all or nothing kind of thing. Just make efficient tables and that won't be an issue

might be right there, i am not sure, running vpinmame 3.4 at the moment (https://github.com/v...pinmame/actions)

any way to test if at91jit works?
know any particular tables that crash if it doesnt?
Just for curiosity sake.

 

It's not something anyone would throw on their cab, cause it needs all 64bit helpers to go with it, and they dont all come in that flavor

though i guess, one day, MS may go the apple route, and ditch 32bit support on us

But that is not this day.

[Thalamus]

Many of the modern Sterns need to have at91jit enabled for timing purposes. Mustang, TWD and Star Trek all, according to DjRobX needs it. But, I think it is a good idea to test this out from time to time. Pinmame is like any other of these fine programs under constant change and I have noticed that several of my known to crash situations have vanished lately. Most of them where known to start acting up with at91jit combined with dmddevice. I haven't tried 64bit on pinmame for a long time myself. If you are going to test it. Try with at91jit both enabled and disabled. Look for dmd getting out of sync with the game. You might have to play the machine for a while though.

[DKong]

I see quite a few tables recently uploaded require vpx 10.7 beta to run. Is the most recent build considered stable and does this mean 10.7 is close to an official release?

[toxie]

We're getting nearer at least. 

 

As for 32 vs 64bit builds: Thalamus nailed it with his explanations. Also, at the moment there is no real benefit (except for larger address space, i.e. more RAM available to tables) for using 64bit builds. Performance is usually pretty much the same (unless at91jit is triggered (Stern), then even x86/32bit always wins at the moment).

[Friffy1]

I see quite a few tables recently uploaded require vpx 10.7 beta to run. Is the most recent build considered stable and does this mean 10.7 is close to an official release?

 

There's no permanent change happening so there's no reason not to try it.  If you run into issues, switch back, or run them both side-by-side.

[Thalamus]

I you where to ask me. Yes. Go for it. At last it is now so good that we should get more feedback from it. Rename your current VPinballX.exe to VPinball106.exe or something. If you at any point want to go back. Just renamed your VPinballX.exe to VpinballX107beta.exe and rename the other one back to VPinballX.exe.

 

Under keys/dof preferences, know that there is a new plunger that is enabled. It might for some tables do odd things. So, turning it off ( default - currently it is on ) might be a solution you find satisfying, until the tables themselves has fixes.

[toxie]

32bit vs 64bit: But: You can also have both installed at the same time, if you really like. Same goes for (V)PinMAME.

Edited by toxie, 06 April 2021 - 08:05 PM.

[wiesshund]

Many of the modern Sterns need to have at91jit enabled for timing purposes. Mustang, TWD and Star Trek all, according to DjRobX needs it. But, I think it is a good idea to test this out from time to time. Pinmame is like any other of these fine programs under constant change and I have noticed that several of my known to crash situations have vanished lately. Most of them where known to start acting up with at91jit combined with dmddevice. I haven't tried 64bit on pinmame for a long time myself. If you are going to test it. Try with at91jit both enabled and disabled. Look for dmd getting out of sync with the game. You might have to play the machine for a while though.

 

I dont mind testing it, just to see how it is working currently, for observations sake.
are you by any chance able to compile a 64bit b2sServer?
 

I will set ST to auto play for a while a91jit is enabled
i will see how bad it can get

[wiesshund]

@Thalamus

 

Well, interestingly enough

VPX 10.7 64bit with
VPinMAME 3.4 64bit
With freezys 1.9.1 r10 64bit
Is still running Star Trek LE 1.61, in sync even.
Table has been on auto play for almost 3 hours (and the only time i will EVER roll the score board LOL)

this is with at91jit on.

 

I will try it later with it off.

I know we do not need it now, but i guess is kind of nice to know what state it is in, since it probably does not get tested much as a whole package.

 

Of course, when you guys start getting 8k playfield screens....  
 

[wiesshund]

Ok, so, you can not actually roll over the scoreboard

It just keeps going in the trillions

 

I am stopping it now, but it was still in  sync, and no crash or anything.

If someone could help me do a 62bit b2s, i'd be willing to kick it around for a bit
see how it works in regular use

[lukpcn]

Table has been on auto play for almost 3 hours (and the only time i will EVER roll the score board LOL)

this is with at91jit on.

 

I will try it later with it off.

I know we do not need it now, but i guess is kind of nice to know what state it is in, since it probably does not get tested much as a whole package.

 

Of course, when you guys start getting 8k playfield screens....  
 

What is the autoplay ?

[wiesshund]

 

Table has been on auto play for almost 3 hours (and the only time i will EVER roll the score board LOL)

this is with at91jit on.

 

I will try it later with it off.

I know we do not need it now, but i guess is kind of nice to know what state it is in, since it probably does not get tested much as a whole package.

 

Of course, when you guys start getting 8k playfield screens....  
 

What is the autoplay ?

 

 

i rigged the table to play itself

 

Sadly, it was much more impressive than my playing

Edited by wiesshund, 07 April 2021 - 07:14 AM.

[juju1976]

Hello probably i miss something but i cannot get table properties with this beta.

I meen i always get un Layer properties, i have no more option button in toolbar

 

do you someone know how to reactivate options for table ?

 

https://drive.google...iew?usp=sharing

 

thanks a lot

[toxie]

this is with at91jit on.

 

I will try it later with it off.

don't need to do that.. at91jit is not supported on x64, so its always off there.

Hello probably i miss something but i cannot get table properties with this beta.

I meen i always get un Layer properties, i have no more option button in toolbar

 

do you someone know how to reactivate options for table ?

 

https://drive.google...iew?usp=sharing

 

thanks a lot

Could you please upload to something that is accessible publically?

[juju1976]

https://i.postimg.cc...Fm/IMG-7623.jpg

 

this is the picture

Edited by juju1976, 07 April 2021 - 04:08 PM.

[barneyrfd]

Hello

 

Installed VPX 10.7 and tried several tables.  Had to install flexdmd to get them to run.  I did that and the tables run so I assume flexdmd is working.  But...I do not have any form of dmd on any of the tables.  The F1 key does nothing, no menu, nothing.  No other F keys work either.

 

Just wondering if anyone else has this problem and how it might be corrected. Thanks.

 

cheers

[juju1976]

Ok sorry i fount it i just need to open with mouse the windows between properties and layer

 

thanks