4027 replies to this topic

[toxie]

New build which tweaks the ogg/mp3 PlaySound volume once more: https://github.com/v...7.0-133-67fe160

This should hopefully also fix the PinMAME altsound issue.

[toxie]

 

 

When using -minimized command line param I can't see the progress bar when loading from frontend but can't use Q button to pause the VPX while playing

When not using -minimized I see the progress bar window when loading a table but can use Q for pauing the gameplay....

Can We have a param for just hiding the progress bar window ? something line -NoLoadingBar or something ? That would allow to have no progress bar and still be able to pause vpx...

I added a new paramater "-ExtMinimized" which does that. In addition, it will directly leave also the editor when quitting from the pause menu.

The VP installer will also use that then from now on when installing the registry entry for playing (double clicking a table).

 

See https://github.com/v.../runs/716664509

 

 

I've checked the ExtMinimized param, the loading is gone, pause works but had no focus on the resume button, needed to use mouse...

Without the ExtMinimized param used, the progress bar is there, and pause menu has focus on the resume button so I can unpause right away.
Will have some additional testing tomorrow - maybe it was "happeden once" thing in popper.
 

 

Did you check again? Cause for me the focus is always on resume..

[wiesshund]

if i pause table and then hit enter or escape it resumes

if i hit Q again, it of course quits to editor

if i hold Q or hold escape then it exits completely

 

this is using extminimized

 

I believe this is the intended behavior?

 

when using minimized the above is still true
except that you can not see the pause menu
which is also intended behavior?

[toxie]

Yes and yes

[batch]

What are the main evolutions / improvements in VP10.7 with regard to VP10.6 ?

 

And will there be a stable version of VP10.7 soon ?

 

I ask these questions because I plan to work again on my table "L'Hexagone" (I've been very lazy since the beginning of this year ! )

 

and I want to be sure that as many people as possible will download it, when it's finished (not before a few months)

Edited by batch, 12 April 2021 - 09:25 AM.

[jpsalas]

For the improvements read the Changelog.txt that comes with 10.7. There are a lot of changes But I must say that when editing tables it is much more stable than 10.6. 10.6 could crash just to copy/paste something from another table.

But I guess it is up to fuzzel and toxie to say when it will be the official release

[fuzzel]

We don't have a specific date in mind or planned to release the 10.7.
We release a new version when we feel the current beta is stable enough an no new features are added meanwhile.

[batch]

Thanks, JP is a good salesman, so I'm gonna work with VP10.7

 

But I'll sure ask many questions !

[Segovia11]

@juju1976 : Download this regsitry export, save it to the desktop or somewhere convenient. https://www.dropbox....gistry.reg?dl=0 - then double click it and accept the change. It can be a convenient thing to export your vpinball registry keys at a point where everything is setup like you want it. Then if odd things like this happens, well, you kind of do the same. Restore the registry.

 

@barneyrfd : Your question doesn't belong in the beta thread. Please ask it in support thread for the table. IF it is for all tables, well, start a new topic, and, don't use the beta thread for personal install problems.

 

Dear Thalamus, barneyrfd post report dated 7 Apr 2021 at 0915am was a 10.7 issue. 10.7 is a beta product and this is the 10.7 beta thread. barneyrfd was using the right thread to report his concerns.  

He said Quote "The F1 key does nothing, no menu, nothing. No other F keys work either." and he was referring to the installed VPX 10.7. He may have identified a 10.7 beta error.

 

With VPX_7_beta_rev129

F2 opens the sound manager without errors

F3 opens the sound manager without errors

F4 opens the Material manager without errors

F5 plays the table without errors

F6 opens the interactive edit table without errors

F8 opens the collection manager without errors

Nothing on F7,F9,F10,F11 & F12

 

Development Team please find enclosed a VPX_7_beta_rev129 bug report 

1. From the main editor position VP10.7 crashes when you press F1. It also manufactures a dump file & a crash report.

 

The following only occurs when you have fonts in the font manger

1. When it crashed the VPTemp0,VPTemp1 & VPTemp2 files are not deleted. I guess, when Visual Pinball does not close down properly, it is unable to delete the VPTemp files.

2. After it crashes you must first log out & delete the VPTemp files manually.

3. "The temporary file C:\VisualPinball\VPTemp0.tff could not be written" error will not occur after the VPTemp file has been manually deleted.

4. The error only occurs after a crash & the VPTemp file must be deleted before running Visual Pinball again.

5. VPTemp errors do not occur if Visual Pinball does not crash. (Bug rectified) 

[toxie]

We don't have a specific date in mind or planned to release the 10.7.
We release a new version when we feel the current beta is stable enough an no new features are added meanwhile.

At least the ogg/mp3 sound volume issue is now solved, which was a major bummer. Now "only" fixing more bugs is on the table i think.

Thanks, JP is a good salesman, so I'm gonna work with VP10.7

 

But I'll sure ask many questions !

Changelogs:

https://github.com/v...t/Changelog.txt

https://github.com/v...log_Scripts.txt

https://github.com/v...ndReference.txt

[Thalamus]

@segovia11 : Sure, it will happen that a user is actually having a issue with a 10.7 feature. But, if everyone that crash their vpx and are referring to dmd not working and no F-keys and they are actually working. Then you should start at a different thread. It is not a good idea to default to the beta channel for errors. The recent problem with pinmame and altsound is a good example on how it best should be handled. Once we know it is related - then head over here for a bug report.

 

I'm wondering, why are you an expert on these font files ? Are you vpx unstable, or are you just trying to provoke errors to find a pattern ? I can only remember to have seen that error once or twice.

[Segovia11]

@segovia11 : Sure, it will happen that a user is actually having a issue with a 10.7 feature. But, if everyone that crash their vpx and are referring to dmd not working and no F-keys and they are actually working. Then you should start at a different thread. It is not a good idea to default to the beta channel for errors. The recent problem with pinmame and altsound is a good example on how it best should be handled. Once we know it is related - then head over here for a bug report.

 

I'm wondering, why are you an expert on these font files ? Are you vpx unstable, or are you just trying to provoke errors to find a pattern ? I can only remember to have seen that error once or twice.

 

Dear Thalamus,

This forum is for remarks that will benefit the development Team & all Visual Pinball users regardless to how trivial you may think it is. Your last comment opposes that good practice.  

Barneyrfd had an issue with F keys and there is a F1 key error which has been reported in.

You should take advantage when exchanging knowledge - regardless to an individuals error tracking attitude which is similar to yours.

All Visual Pinball users regardless of level of experience will now know how to resolve a VPTemp error issue after a crash. This is only applicable to Tables that have Fonts in the Font Manager. 

The VPTemp error is now resolved for me & hopefully for other users that may have had similar issues. 

I hope 10.7 beta users take advantage of the period they have whilst it is active in regard to the exchange of information and bug reports.   

The Devs have supported that attitude & I am sure they will continue to. 

[Thalamus]

Not going to discuss in this thread - I acknowledge that it was a valid error report by Barneyrfd, which I later contacted via PM I should add. And yours. I'm still firm believer in keeping this thread as light as possible for good error reporting. Yours is, the other one was confusing, even by the author, just updating and not being clear as to if it was a dmd error or F-key issues. If you want this further discussed. Please start a thread, somewhere else.

[wiesshund]

 

Development Team please find enclosed a VPX_7_beta_rev129 bug report 

1. From the main editor position VP10.7 crashes when you press F1. It also manufactures a dump file & a crash report.

 

 

 

F1 crash

Crash report VPX rev127 (c9c069f)
============
Process: VPinballX.exe
Reason: 0xE06D7363 - UNKNOWN at 0023:76D9A6E2
Thread ID: 0xD94 [3476]

Call stack
==========
76D9A6E2 KERNELBASE.dll RaiseException + 0x62 (0xFFFFFFFFE06D7363 0x00000001 0x00000003 0x0019dfd0)
005D50B0 VPinballX.exe (0x0019E000 0x0075A1EC 0x00000053 0x0019ebbc)
00426092 VPinballX.exe (0x0075A1EC 0x00000053 0x0019EBBC 0x0019e298)
0019E000  (0xFFFFFFFFCCCCCCCC 0x5651CCCC 0x247C8B57 0x74ff8510)
CCCCCCCC  (0x5651CCCC 0x247C8B57 0x74FF8510 0xffffffffd00d8b14)
CCCCCCCC  (0x247C8B57 0x74FF8510 0xFFFFFFFFD00D8B14 0x57007617)
5651CCCC  (0x74FF8510 0xFFFFFFFFD00D8B14 0x57007617 0x001b59e8)
247C8B57  (0xFFFFFFFFD00D8B14 0x57007617 0x001B59E8 0xffffffff85f08b00)
74FF8510  (0x57007617 0x001B59E8 0xFFFFFFFF85F08B00 0xffffffffeb2f75f6)
D00D8B14  (0x001B59E8 0xFFFFFFFF85F08B00 0xFFFFFFFFEB2F75F6 0xffffffffa1f63302)
57007617  (0xFFFFFFFF85F08B00 0xFFFFFFFFEB2F75F6 0xFFFFFFFFA1F63302 0x007617d0)
001B59E8  (0xFFFFFFFFEB2F75F6 0xFFFFFFFFA1F63302 0x007617D0 0x00c4b0ff)
85F08B00  (0xFFFFFFFFA1F63302 0x007617D0 0x00C4B0FF 0x15ff0000)
EB2F75F6  (0x007617D0 0x00C4B0FF 0x15FF0000 0x0060e368)
A1F63302  (0x00C4B0FF 0x15FF0000 0x0060E368 0x1674c085)
007617D0 VPinballX.exe (0x15FF0000 0x0060E368 0x1674C085 0xfffffffff685308b)
00C4B0FF VPinballX.exe (0x09126100 0x00000000 0x00000000 0x00000000)
095ECF80  (0x00000000 0x00000000 0x00000000 0x00000000)
09126100  (0x00000000 0x00000000 0x00000000 0x00000000)

Environment
===========
Date/time: 12/4/2021, 14:25:23:481
Number of CPUs: 4
Processor type: 586
System: Windows 10 (10.0 19042)

Memory status
=============
Total Reserved: 63948K (62M) bytes
Total Commited: 270556K (264M) bytes
Total Free: 3859736K (3769M) bytes
Largest Free: 2095552K (2046M) bytes

Registers
=========
EAX=0019DF50 EBX=19930520 ECX=00000003 EDX=00000000
ESI=03136870 EDI=0075A1EC EBP=095ECF80 ESP=007617DC EIP=09126100
FLG=00000216 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B


Mini dump saved successfully.

[wolis]

In 10.7.0 the properties bar on the right does not have a  vertical scroll bar for showing long content.

 

Try resizing your window vertically - you get no scrollbar - but if you resize horizontally you get a horizontal scroll bar.

 

Any chance you can add a vertical scroll bar for us that have small screens?

[wiesshund]

In 10.7.0 the properties bar on the right does not have a  vertical scroll bar for showing long content.

 

Try resizing your window vertically - you get no scrollbar - but if you resize horizontally you get a horizontal scroll bar.

 

Any chance you can add a vertical scroll bar for us that have small screens?

what size is your screen? and are you using any kind of increased scaling?

 

It does not scroll, i even snapped it off the dock and squished it, no vertical scroll bar

but at 768 pixel screen height, there was nothing to be scrolled either, even down to 1280x720 it everything fit in the bar with out needing to scroll
unless i set scaling to something like 200% (maybe even 150%)

 

So for now, if you turn off scaling, you should be ok until it gets a scroll bar, it's a work around anyways

If you are not using scaling, do you have a rez smaller than 1280x720? (and that is pretty small, netbook territory there)

 

10.6 has no scrolling either, but it also lacks the tabs, so it is more annoying since you have to click the expanders constantly

[wolis]

Not sure if this is the right place for a suggestion.. but it would be great if we could assign all possible keys to keyboard keys.

 

I don't have a controller but I do have a small programmable board that emulates a keyboard.

 

It seems like some keys (PinMAME coins and door) can be assigned. Unlike flippers. 

[wiesshund]

Not sure if this is the right place for a suggestion.. but it would be great if we could assign all possible keys to keyboard keys.

 

I don't have a controller but I do have a small programmable board that emulates a keyboard.

 

It seems like some keys (PinMAME coins and door) can be assigned. Unlike flippers. 

 

You can already, unless i am not understanding you

 

Most keys can be set in vpx under prefs in the dof /  nudge option

And some keys that fall under the direct domain of vpinmame and are not directly used by vpx can be changed in vpmkeys.vbs

[wolis]

You can already, unless i am not understanding you

 

Most keys can be set in vpx under prefs in the dof /  nudge option

And some keys that fall under the direct domain of vpinmame and are not directly used by vpx can be changed in vpmkeys.vbs

 

 

Ah.. thanks!

 

Handy hint re vpmkeys.vbs - I had no idea.  Maybe we can add some text near the PinMAME buttons hinting at this?

 

I have a silly PC keyboard layout with no normal END key and it is proving difficult opening the coin door to change the volumes :-)

Edited by wolis, 13 April 2021 - 09:21 AM.

[wiesshund]

 

Good to know the vertical scroll-bar is on its way.

 

 

 

You maybe misunderstand, i dont know if one is coming, though i dont guess adding one would be too terrible for them to do

 

Also, when you crunch it small enough to make a scroll bar appear, i think you will find it does not actually scroll
not the entire panel, it only scrolls a small amount.

 

But in sub full screen, if you keep the window at least 720 pixels tall, you should still have the full options bar.
Same thing for the tool bar on the left

 

 

 

Handy hint re vpmkeys.vbs - I had no idea.  Maybe we can add some text near the PinMAME buttons hinting at this?

 

I have a silly PC keyboard layout with no normal END key and it is proving difficult opening the coin door to change the volumes :-)

 

 

It's in one of the doc files that comes with VPX but i forget which one.

I think between that, and the heading saying pinmame buttons, and the fact you cant click them

someone probably figured that would give a person a clue, though it isnt quite the clue i was looking for
(as defined in vpmkeys.vbs)  would have been a wee bit more helpful  of a hint

 

On my desktop, i basically have everything on the numeric keypad
coins, start, buyin, coin door, slam tilt, rom menu options(7890) etc

 

So it will let you move anything that happens post table launch between one of those 2 places

 

It depends on if the script declares the function as to which place it is going to listen to

 

if table script says

if key = addcoinkey then blah blah
Then it will listen to the key you set in dof / nudge

(and it probably follows that with a controller.switch command, if it is a ROM table)

 

otherwise, if the table makes no mention of adding coins, then it is left solely to vpinmame
and some how vpmkeys.vbs gets used to give vpinmame its new keymap

not sure when/how it actually calls it up, i have never really looked at the source to find out

but it beats going to each ROM and hitting tab and picking Input for This Game

and setting them

Edited by wiesshund, 13 April 2021 - 09:18 AM.