MagicEngine

[Chris]

latest beta crashes on my computer, previous versions work just fine

Win98SE/Core2Duo/512Ram/MatroxG400/SoundBlaster128PCI


and here's log

[VIDEO INIT]
driver... DirectX
device: v0.0.0 (HAL)

[INPUT INIT]
opening direct input DLL... OK
init direct input... OK
scanning gamepad device(s)...
- gamepad 0 : Dual USB Force Feedback Joypad (MP-8866) (buttons=12, axes=4, povs=1, guid=D346F900-2101-11DC-8001444553540000)
- gamepad 1 : Dual USB Force Feedback Joypad (MP-8866) (buttons=12, axes=4, povs=1, guid=D442BE20-2101-11DC-8002444553540000)
found 2 gamepad(s)

[SOUND INIT]
scanning sound card... found 1 sound card(s)
checking sound card mixer ("SB PCI128 Mixer" v4.6... OK
+SPEAKERS: vol = 49 [00000000/0000FFFF]
-COMPACTDISC [ 0] vol = 49 [00000000/0000FFFF] (selected as CD input line)
-WAVEOUT [ 1] vol = 49 [00000000/0000FFFF]
-SYNTHESIZER [ 2] vol = 49 [00000000/0000FFFF]
-MICROPHONE [ 3] vol = 49 [00000000/0000FFFF]
-AUXILIARY [ 4] vol = 81 [00000000/0000FFFF]
-AUXILIARY [ 5] vol = 49 [00000000/0000FFFF]
-AUXILIARY [ 6] vol = 78 [00000000/0000FFFF]
-TELEPHONE [ 7] vol = 49 [00000000/0000FFFF]
+WAVEIN:
master audio volume... 49 (49)
wav audio volume... 49 (49)
cd audio volume... 49 (49)
opening direct sound DLL... OK
init direct sound... OK
set cooperative level... OK
create primary buffer... OK
setup primary buffer: freq=44100 channels=2 bits=16... OK
create thread... OK

[CD-ROM INIT]
scanning drives...
opening ASPI DLL... OK
found 5 adapters
+ drive 0: ZTekWare OCDE (port=0, unit=0) [CDROM]
+ drive 1: SAMSUNG CDRW/DVD SM-352B (port=1, unit=0) [CDROM]
+ drive 2: TSSTcorp CD/DVDW SH-W162C (port=1, unit=1) [CDROM]
+ drive 3: Generic DVD-ROM (port=2, unit=0) [CDROM]
+ drive 4: MagicISO Virtual DVD-ROM (port=3, unit=0) [CDROM]
+ drive 5: MagicISO Virtual DVD-ROM (port=3, unit=1) [CDROM]
+ drive 6: MagicISO Virtual DVD-ROM (port=3, unit=2) [CDROM]
+ drive 7: MagicISO Virtual DVD-ROM (port=3, unit=3) [CDROM]
found 8 CD-ROM drive(s)

[CDDA INIT]
creating thread... OK

[CD SCAN INIT]
creating thread... OK

[GAMEPAD INIT]
auto calibration: -500 500

[PSG INIT]
allocating sound buffers(6)... OK
allocating ADPCM sound buffer [0]... OK
allocating ADPCM sound buffer [1]... OK

[GAMEPAD STATS]
gamepad 0 stats:
status: 0000
poll errors: 0 0 0 0
poll: failed=0 success=0
axes (4):
- 0: min=268435456 max=-268435456 [0 (0 / 0)]
- 1: min=268435456 max=-268435456 [0 (0 / 0)]
- 2: min=268435456 max=-268435456 [0 (0 / 0)]
- 3: min=268435456 max=-268435456 [0 (0 / 0)]
povs (1):
- 0: min=268435456 max=-268435456 [0 (0 / 0 / 0 / 0)]
buttons (12):
- 0: off=0 on=0 bitmask=00
- 1: off=0 on=0 bitmask=00
- 2: off=0 on=0 bitmask=00
- 3: off=0 on=0 bitmask=00
- 4: off=0 on=0 bitmask=00
- 5: off=0 on=0 bitmask=00
- 6: off=0 on=0 bitmask=00
- 7: off=0 on=0 bitmask=00
- 8: off=0 on=0 bitmask=00
- 9: off=0 on=0 bitmask=00
- 10: off=0 on=0 bitmask=00
- 11: off=0 on=0 bitmask=00

[GAMEPAD STATS]
gamepad 1 stats:
status: 0000
poll errors: 0 0 0 0
poll: failed=0 success=0
axes (4):
- 0: min=268435456 max=-268435456 [0 (0 / 0)]
- 1: min=268435456 max=-268435456 [0 (0 / 0)]
- 2: min=268435456 max=-268435456 [0 (0 / 0)]
- 3: min=268435456 max=-268435456 [0 (0 / 0)]
povs (1):
- 0: min=268435456 max=-268435456 [0 (0 / 0 / 0 / 0)]
buttons (12):
- 0: off=0 on=0 bitmask=00
- 1: off=0 on=0 bitmask=00
- 2: off=0 on=0 bitmask=00
- 3: off=0 on=0 bitmask=00
- 4: off=0 on=0 bitmask=00
- 5: off=0 on=0 bitmask=00
- 6: off=0 on=0 bitmask=00
- 7: off=0 on=0 bitmask=00
- 8: off=0 on=0 bitmask=00
- 9: off=0 on=0 bitmask=00
- 10: off=0 on=0 bitmask=00
- 11: off=0 on=0 bitmask=00

[dmichel]

From the log everything seems OK. How does it crash exactly, does Windows report an error? And does it crash before or after a window is opened?
_________________
David Michel

[Chris]

it crashes BEFORE, btw it only crashes on WinME/SE but not on WinXP Duel booting (same hardware config)

previous versions still works fine on both WinSE and WinXP


I think problem is 'success=0' in [GAMEPAD STATS]

log resulted in crash (WinSE) :

.
.
.
.

[GAMEPAD STATS]
gamepad 1 stats:
status: 0000
poll errors: 0 0 0 0
poll: failed=0 success=0
axes (4):
- 0: min=268435456 max=-268435456 [0 (0 / 0)]
- 1: min=268435456 max=-268435456 [0 (0 / 0)]
- 2: min=268435456 max=-268435456 [0 (0 / 0)]
- 3: min=268435456 max=-268435456 [0 (0 / 0)]
povs (1):
- 0: min=268435456 max=-268435456 [0 (0 / 0 / 0 / 0)]
buttons (12):
- 0: off=0 on=0 bitmask=00
- 1: off=0 on=0 bitmask=00
- 2: off=0 on=0 bitmask=00
- 3: off=0 on=0 bitmask=00
- 4: off=0 on=0 bitmask=00
- 5: off=0 on=0 bitmask=00
- 6: off=0 on=0 bitmask=00
- 7: off=0 on=0 bitmask=00
- 8: off=0 on=0 bitmask=00
- 9: off=0 on=0 bitmask=00
- 10: off=0 on=0 bitmask=00
- 11: off=0 on=0 bitmask=00



logs working fine (WinXP)

.
.
.
.
.
[GAMEPAD STATS]
gamepad 1 stats:
status: 0000
poll errors: 8007000c 0 0 0
poll: failed=0 success=1418
axes (4):
- 0: min=-8 max=0 [1418 (0 / 0)]
- 1: min=-8 max=0 [1418 (0 / 0)]
- 2: min=-8 max=0 [1418 (0 / 0)]
- 3: min=268435456 max=-268435456 [0 (0 / 0)]
povs (1):
- 0: min=-1 max=-1 [1418 (0 / 0 / 0 / 0)]
buttons (12):
- 0: off=1418 on=0 bitmask=00
- 1: off=1418 on=0 bitmask=00
- 2: off=1418 on=0 bitmask=00
- 3: off=1418 on=0 bitmask=00
- 4: off=1418 on=0 bitmask=00
- 5: off=1418 on=0 bitmask=00
- 6: off=1418 on=0 bitmask=00
- 7: off=1418 on=0 bitmask=00
- 8: off=1418 on=0 bitmask=00
- 9: off=1418 on=0 bitmask=00
- 10: off=1418 on=0 bitmask=00
- 11: off=1418 on=0 bitmask=00

[Chris]

oh...windows does not report any error when crash..

[dmichel]

Apparently it's not really a crash, it seems like if ME auto exited itself, no idea why though, if there was an error ME would report it, strange... The gamepad 'success' stats is 0 in the first log because the main program loop didn't start, it exit before.
_________________
David Michel

[Chris]

found the cause...it seems now i can't use any full-screen modes..only windowed or desktop mode works...any clue ?
again previous versions fine

[dmichel]

Ah, I see. Is ME configured to use DirectX or OpenGL?

This might be because of the new video startup code, it can switch to fullscreen without a window being displayed, maybe this doesn't work with WinME.
_________________
David Michel

[Chris]

Yes, I think that's the cause as it 'CLOSES' (not crash) on my computer at office too (WinME)
btw, I use Directx by default

[dmichel]

If you start it in windowed mode can you select a fullscreen mode after inside the emulator or does that make it closes too?
_________________
David Michel

[Chris]

Yes, it closes/crashes too, as soon as you select any full-screen resolution, even 640x480....i tried every settings and tweaks from Menu and INI, but no luck...

[dmichel]

Try with this test version and add these lines in the pcfx.ini file :

[video]
hide_startup_window=n

With this option MEFX will use the old startup code.

Let me know.
_________________
David Michel

[Chris]

well i found the exact cause that crashed MEFX when switched to full-screen mode...this is nothing to do with 'new startup code', but something to do with the number of resolutions supported by your windows display driver
my current WinME driver supports more than 200 resolutions including custom ones, while WinXP driver less than 30 resolutions..
so for the test purpose, I added more custom resolutions to my WinXP display driver,probably about another 100, guess what ?
it crashed on WinXP too....in other words, it runs fine even on WinME, if the number of supported resolution is less than 50...Yes, I tested (reverted back to nVidia stock driver) ..it works !!

assumably it crashes while searching for availble full-screen modes ,so
maybe you rather include the code that can skip that 'mode detection routine' or unlimit/increase the number of resolution can be supported...


take care

[Chris]

**UPDATE**

if you select low resolution mode like 256x240 or set as default custom resolution or Full-screen mode, MEFX gives 'Blue Screen' (WinME) and completely locks up/crash (WinXP)..(the only solution -> reboot) ,but if you change your desktop resolution to 256x240, and then select 'desktop' from MEFX menu, 256x240 mode works...

[Chris]

**UPDATE** 2

it 'sometimes' crashes , now it works O.K.
i don't know what caused that crash...currently i'm fiddling with options in INI...also that 'CUSTOM' option in display menu setting ,most of time, doesn't appear in the menu, (but rarely shows up )and custom resolution option seems doesn't work ...always use what's in 'fullscreen resolution' setting instead, even it is set to 'ON' (custom_resolution=y) through INI


here's my video setting


# ----
# video settings
# ----
#

[video]

;
; driver
; --
; 0 -> DirectX [default]
; 1 -> OpenGL
;

driver=0

;
; windowed mode
; --
;
; y -> windowed [default]
; n -> fullscreen
;

windowed=n

;
; fullscreen resolution
; --
;

screen_width=640
screen_height=480
screen_depth=16

;
; screen aspect ratio
; --
; 0 -> none
; 1 -> 4/3 (298 x 224) [default]
; 2 -> 3/2 (336 x 224)
; 5 -> fullscreen
;

screen_ratio=0,0

;
; desktop mode
; --
;
; y -> enable
; n -> disable [default]
;

desktop=n

;
; video sync
; --
; 0 -> disable [default]
; 1 -> enable
; 2 -> vsync + timer
; (special mode to use when the screen refresh rate is higher
; than 60 fps or when running the emulator in windowed
; mode)
;

vsync=1,1

;
; frame skip
; --
; 0 -> disabled [default]
; 1 -> skip 1 frame
; 2 -> skip 2 frames
; ..
;

frameskip=

;
; fullscreen stretch
; --
;
; y -> enable
; n -> disable [default]
;

fullscreen=0,0

;
; zoom
; --
; 0 (x1).. 5 (x6)
;

zoom=1,0

;
; filtering mode
; --
;
; 0 -> disable [default]
; 1 -> bilinear filtering
;

filter=1,0

;
; scanlines:
; --
; 0 (no scanlines) .. 40 (black scanlines)
;

scanlines=0,0
scanlines_pattern_2=0,255
scanlines_pattern_3=0,0,255
scanlines_pattern_4=0,0,255,255
scanlines_pattern_5=0,0,0,255,255
scanlines_pattern_6=0,0,0,255,255,255

;
; gamma correction:
; --
; adjust gamma level (0 .. 40)
;

gamma=20,20

;
; contrast control:
; --
; adjust contrast (0 .. 40)
;

contrast=20,20

;
; saturation control:
; --
; adjust color saturation (0 .. 40)
;

saturation=20,20

;
; brightness control:
; --
; adjust brightness (0 .. 40)
;

brightness=20,20

;
; custom screen resolutions
; --
; custom screen resolutions to be used for the different
; PC-FX video modes (256x224, and 336x224) and for the GUI
;
; y -> enable
; n -> disable [default]
;
; custom_resolution=y
; res_256=256,240
; res_336=400,300
; res_gui=512,480
;
;

custom_resolution=y
res_256=256,224
res_336=336,224
res_gui=640,480

hide_startup_window=y

tripple_buffer=y

[Chris]

never mind...now everything works just fine except that windowed mode <-> full-screen problem ,of course...
it was "stretch' setting which i put wrong(?) value (for some reason , it must be set to '1' for custom mode) caused fatal crash

p.s. just one little annoyance though, mouse pointer shows up everytime MEFX switches to different custom mode 336x224<->256x224...
it would be good idea that we can disable mouse function in game and only can be activated in GUI