141 replies to this topic

[batch]

I think that's because the table is too stretched

 

 

With these settings I also get the ball above the apron (the ball is far from being spherical)

 

There shouldn't be these angles at the bottom of the table

 

And you can check the square "visible" for primitives sidewallleftDT & sidewallrightDT

[wiesshund]

Well, i re-downloaded table.
Same POV, and it does not do it
but the previous download (i named the new download 1.2b.vpx) still does it.

very strange, maybe my download got some kind of minor bit error  corruption? cause flupper has not changed the table since then.

 

go figure.
Good to know it is not the table itself.

 

@batch
Maybe also try redownloading, cause my redownload does not display what you also see in the editor view, where your lockdown bar is beveling strangely outwards

 

Here is after redownloading

 

Looks fine on my pc also.   

Hey, what backdrop is that?
And where is the Cat?

[clyde]

The backdrop is on page 7 in the desktop backdrops thread, & the cat ran away from home.

[Mitchell]

Yeah that is weird. Table shouldn't be loading on corrupted. Weird if it did.

[wiesshund]

Yea, really freaky, but oh well.
Now i can play the new version without feeling like it was painted by Salvador Dali

[batch]

These are not my desktop settings, I was just trying to understand why you got this problem

 

No trouble with this version, and nice to see you found the solution to yours

 

I did a backdrop for this fantastic table, and, next week, I'll upload it with 199 other ones

 

Here is a snapshot

 

[strangeleo72]

Crash report VPX rev4188

============

Process: vpinballx10.6.exe

Reason: 0xC000001D - EXCEPTION_ILLEGAL_INSTRUCTION at 0023:5E579D87

Thread ID: 0x7A8 [1960]

 

Call stack

==========

5E579D87 nvd3dum.dll (0x0871E718 0x48F02678 0x48F05401 0x00000000)

5E57B7AE nvd3dum.dll (0x00000001 0x00000000 0x00000000 0x00000000)

5E57C6EE nvd3dum.dll (0x48F02678 0x00000011 0x48F05430 0x0871e718)

5E5BE360 nvd3dum.dll (0x48F05448 0x00000043 0x48F02678 0x5e64be9f)

5E5C3000 nvd3dum.dll (0x35DEE9D8 0x0871E888 0x5E4CE035 0x48f02678)

5E4C9B84 nvd3dum.dll (0x48F02678 0x48F02678 0x48EF79E0 0x355dd560)

5E4CE035 nvd3dum.dll (0x5F4A5140 0x0000007E 0x48F02678 0x48ef79e0)

5E49CC5E nvd3dum.dll (0x1141B4F0 0x48EF79E0 0x48F02678 0x5ec4207b)

5E49D48D nvd3dum.dll (0x355DD560 0x0871FE8C 0x0871FE88 0x0871ff10)

5EC1B373 nvd3dum.dll (0x00000000 0x00000000 0x00000000 0x35d95130)

5EC1B98F nvd3dum.dll (0x00000001 0x3A167998 0x3A16778C 0x4901f240)

5ED951C2 nvd3dum.dll (0x3A167480 0x35D95130 0x00000003 0x0a625d38)

5EDA520F nvd3dum.dll (0x4901F240 0x0ADFEFDA 0x5F06650B 0x5f06650b)

5F066563 nvd3dum.dll QueryOglResource + 0x265F23 (0x0A625D38 0x77506340 0x0871FFDC 0x779e7c24)

77506359 KERNEL32.DLL BaseThreadInitThunk + 0x19 (0x0A625D38 0x1FFBBA75 0x00000000 0x00000000)

779E7C24 ntdll.dll RtlGetAppContainerNamedObjectPath + 0xE4 (0xFFFFFFFFFFFFFFFF 0x77A08FEF 0x00000000 0x00000000)

779E7BF4 ntdll.dll RtlGetAppContainerNamedObjectPath + 0xB4 (0x5F06650B 0x0A625D38 0x00000000 0x00000000)

 

Environment

===========

Date/time: 11/11/2020, 17:27:32:454

Number of CPUs: 8

Processor type: 586

System: Windows 10 (10.0 18363)

 

Memory status

=============

Total Reserved: 220904K (215M) bytes

Total Commited: 1137688K (1111M) bytes

Total Free: 2835648K (2769M) bytes

Largest Free: 2095296K (2046M) bytes

 

Registers

=========

EAX=49303608 EBX=48F02678 ECX=493035C0 EDX=00000001

ESI=48F02764 EDI=40000027 EBP=0871FFEC ESP=0871FFE4 EIP=779E7BF4

FLG=00010297 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B

 

 

Failed to save minidump.

[flupper1]

I do not know what to do with a crash dump; does this happen every time you start the table? During gameplay or at the start? And am I correct in seeing that you are using a 10.7 beta version?

[wiesshund]

I do not know what to do with a crash dump; does this happen every time you start the table? During gameplay or at the start? And am I correct in seeing that you are using a 10.7 beta version?

 

Nothing you can do really.

At face value, it looks like his video driver is crashing, which i dont think is a fault of your table
more like your table is simply putting pressure someplace that aint quite right to begin with

@Toxie would be able to tell what the crash means though

 

And no rev 4188 is 10.6.1 final build, non beta
Beta builds are 10.7 rev 43xx

[strangeleo72]

I do not know what to do with a crash dump; does this happen every time you start the table? During gameplay or at the start? And am I correct in seeing that you are using a 10.7 beta version?

No no 

 

i am using 10.6.1 chrash while playing ... I'm playing and crashing. Sometimes it just exits VP and sometimes it hangs windows. Update drivers and stay the same, it's only with the BK2k. VERY RARE

i am using 10.6.1 chrash while playing ... I'm playing and crashing. Sometimes it just exits VP and sometimes it hangs windows. Update drivers and stay the same, it's only with the BK2k. VERY RARE

[strangeleo72]

another advice crash
 

Attached Files

•  IMG_20201111_195825.jpg   99.83KB   5 downloads

Edited by strangeleo72, 11 November 2020 - 11:29 PM.

[wiesshund]

another advice crash
 

You are going to need to get toxie to look at the crash log
to get the exact meaning, he knows the program code, i do not.

 

i dont think it is inherently the table though

[Thalamus]

Normally I've seen Fuzzle debug those crashes and what I've seen him say is that the first line in the crash has to contain VPinball or the crash is actually starting somewhere else than the VPinball.exe itself. So, this sounds very much like what you suggested Wiesshund 4 messages back in this thread.

[Mitchell]

Is there away to turn up the music? I remember the music is louder on some other Black Knight 2000 tables back then.

[wiesshund]

Is there away to turn up the music? I remember the music is louder on some other Black Knight 2000 tables back then.

run the able with the ROM DMD showing (pinmame DMD) or just run the ROM in pinmame32
hit ~ key
arrow up or down to see volumes

music is the ym251 or something like that, 2 of those have to adjust both
Voice is the DAC after it, also 2 of those

default volume for music is kinda low, 9%, try 20%

[Mitchell]

oh ok. Well it is max out on default. Still low. I guessing it my screen speakers is low then. I'll get my speakers out then.

Attached Files

•  Screenshot (87).png   9.64KB   2 downloads

Edited by Mitchell, 13 November 2020 - 01:38 AM.

[wiesshund]

oh ok. Well it is max out on default. Still low. I guessing it my screen speakers is low then. I'll get my speakers out then.

Oh, yea, PC screen speakers, in general SUCK

No one seems to make one with any kind of decent speakers
they are usually little tiny laptop sized speakers, with 0 effort in a creative sound enhancing enclosure

they only seem to work well if you bounce them directly off a hard flat surface.
Thats fine for a laptop with speakers pointed at your table top, not so much for a monitor standing upright in the air.

[Mitchell]

I look up my phone headset to my PC and it louder than the speakers and screen speakers. I tried to hook up the speakers to the front of the PC but it buzzing like crazy. I guess these speakers made for the back of the PC only. Anyway sounds better than before. Using the phone headset and this software too.

 

Oh yeah I did hook the speakers to the screen. Now I have 4 speakers.

Attached Files

•  Screenshot (88).png   296.02KB   2 downloads

Edited by Mitchell, 13 November 2020 - 03:47 AM.

[wiesshund]

If buzzing like crazy, did you plug into mic jack by any chance?

 

In general, front audio panel has same exact wiring as far as a speaker is concerned, than the rear panel does

front panel, in some cases will apply more amplification, for headphones, and only marginal amplification to the rear
so as not to overdrive the signal to an amplifier or amplified speaker.

This does not always hold true on all motherboard audio, the amplification part.
It SHOULD, but it does not, especially in cases where the motherboard repurposes the front panel jacks for 7.1 output.

But buzzing should not be a thing, unless plugging in to the mic jack, in which case the bias voltage might make
a nifty humming noise.

 

And in your screen shot, you got something plugged into the front panel mic jack

[Mitchell]

Yeah it the phone headset. This doesn't do the buzzing noise. The speakers does the buzzing noise. Speakers have a USB plug and a jack point. Probably why the headset jack doesn't like it on the front because the power going through the USB. I have the usb and jack point hook up to the screen but not buzzing noise there.

 

Funny thing is the speakers does the same thing on my old iBuyPower when I have it hook up on the front. lol

 

The screen is hook up on the back. Plug in the speakers jack.

Edited by Mitchell, 13 November 2020 - 05:51 AM.