D3D9: Initialization Fail

[MrGimper]

Hiya,

New to this emulation lark but still own several real Amigas

Running WinUAE 2.3.0 Beta 16 on a netbook (1.6 atom, Intel 945 GFX)

Using a default quickstart but ensuring Direct3D is set, I get the D3D9: Initialization Failed message, which then puts me in DirectDraw mode. However once I click OK and the emu has started, I can F12 and switch to Direct3D no problems.

This happens in fullscreen or windowed. Why won't it start successfully in Direct3D, but allow me to run dDrect3D happily once the emu has started?

thanks

EDIT: I'm running latest DirectX, and have installed latest Filters (1.5.1) from the WinUAE site

[Toni Wilen]

All important information is missing. Log files. (tick logging in misc panel before starting, attach winuaebootlog.txt and winuaelog.txt)

[MrGimper]

Apologies ... files attached.

[Toni Wilen]

Thanks, attach also winuaelog.txt after selecting direct3d "on the fly".

(Unfortunately this seems to be some weird display driver issue, it returns some error code when allocating textures)

[Toni Wilen]

Does it work better if you start winuae with -nod3d9ex command line parameter?

[MrGimper]

Attached

Once the emu had started, I switched to Direct3D with "none" as filter. I also did F12 and switched again to "Null Filter".

I was curious and looked at the log files. When it fails it appears it's trying to create a texture 1504*572 texture allocated, bits per pixel 16. however when switching on-the-fly, it's (successfully) creates a texture 752*286 texture allocated, bits per pixel 32

[MrGimper]

Originally Posted by Toni Wilen

Does it work better if you start winuae with -nod3d9ex command line parameter?

Sorry Toni, missed this.

Yes, if I start with that parameter, I don't get the error.

Out of interest, what does that parameter do?

Thanks v much for your help, and a totally awesome piece of software!

[Toni Wilen]

Originally Posted by MrGimper

Attached

Once the emu had started, I switched to Direct3D with "none" as filter. I also did F12 and switched again to "Null Filter".

I was curious and looked at the log files. When it fails it appears it's trying to create a texture 1504*572 texture allocated, bits per pixel 16. however when switching on-the-fly, it's (successfully) creates a texture 752*286 texture allocated, bits per pixel 32

Try setting null filter before starting.

[MrGimper]

Originally Posted by Toni Wilen

Try setting null filter before starting.

With or without the -nod3d9ex switch?

Will you want the resultant log?

[Toni Wilen]

Originally Posted by MrGimper

With or without the -nod3d9ex switch?

Will you want the resultant log?

Without, because "none" filter option selects same size texture as window and I am quite sure texture size has nothing to do with this issue (at least as long as is stays under 2kx2k)

EDIT: try also http://www.winuae.net/files/b/winuae.zip

[MrGimper]

Originally Posted by Toni Wilen

Without, because "none" filter option selects same size texture as window and I am quite sure texture size has nothing to do with this issue (at least as long as is stays under 2kx2k)

EDIT: try also http://www.winuae.net/files/b/winuae.zip

Nice one Toni.... using the version you supplied I no longer get the error message (not using the -nod3d9ex param).

Thanks very much for sorting this