Steem SSE 3.7 bug reports

[avtandil]

Could you try with this and report messages and TRACE.txt?

http://ataristeven.exxoshost.co.uk/Files/BoilerVC9.zip

It crashed anyway.
Only one message is appearing: Breakpoint pD3D release OK.
Nothing is written to trace.txt

[Steven Seagal]

Thx, same questions with this: http://ataristeven.exxoshost.co.uk/Files/boiler_steem.zip
(Still trying to localise the bug...)

[avtandil]

Thx, same questions with this: http://ataristeven.exxoshost.co.uk/Files/boiler_steem.zip
(Still trying to localise the bug...)

Boiler VC9 - latest:

- Breakpoint: D3D Init OK
- Breakpoint: Disp.Init() completed
- Assert: Disp.pD3D - Abort, Retry, Ignore

if Abort - Trace.txt content:

ram 4352 allocated OK
Display init
Breakpoint: D3D Init OK
nUseMethod 0
Switching to GDI
Passed Disp init D3D9_OK 1
Breakpoint: Disp.Init() completed
Assert failed: Disp.pD3D
Closing TRACE file...

if Retry or Ignore - program crashed, nothing in trace.txt

Boiler Beta BCC:

System error:
The program can't start because FREEIMAGE.DLL is missing from your computer. Try reinstalling the program to fix this problem.
If I put such a file, then CAPSIMG.DLL is reported as missing. Also added.

After that - following message:

The application was unable to start correctly (0xc000007b). Click OK to close the application.

Hope it helps.

Dima-

[Steven Seagal]

Hope it helps.
Dima-

Yes, I see the problem now, thx a lot for your reporting.
D3D9 init succeeds, but you disabled DirectDraw in the Startup options and GDI Init closes D3D at once.
This explains why the exception was reported where it was...
I'll fix the crash tomorrow and upload a new beta. I guess if you disable DirectDraw, you don't care about D3D either.

if Retry or Ignore - program crashed, nothing in trace.txt

That's the violent part.

[avtandil]

Hope it helps.
Dima-

Yes, I see the problem now, thx a lot for your reporting.
D3D9 init succeeds, but you disabled DirectDraw in the Startup options and GDI Init closes D3D at once.
This explains why the exception was reported where it was...
I'll fix the crash tomorrow and upload a new beta. I guess if you disable DirectDraw, you don't care about D3D either.

Yes, I tried R424 - it works normally.
I checked SSE/Boiler VC6 and VC9 - all are working with or without DirectDraw option.

Just Boiler VC9 gives ASSERT: Disp.pD3D when I _DISABLED_ DirectDraw, but if I pressed retry or Ignore - it continues to start and works normally.

We could say that issue was fixed.

Many thanks+

Dima-

[avtandil]

R429 VC6 and VC9 are OK, no any issues found.

[Steven Seagal]

R429 VC6 and VC9 are OK, no any issues found.

Of course.

[axelfoley]

I don't know if this have been reported before. !
Problem with full screen (d3d) using interpolated scanlines. All resolutions tested.
The fullscreen image is to low, missing the last part of the picture at the bottom.
It works fine without interpolated scanlines.
Windows 8.1 nvidia graphic card.

[Steven Seagal]

I don't know if this have been reported before. !
Problem with full screen (d3d) using interpolated scanlines. All resolutions tested.
The fullscreen image is to low, missing the last part of the picture at the bottom.
It works fine without interpolated scanlines.
Windows 8.1 nvidia graphic card.

Welcome to the forum.
(Un)fortunately I can't reproduce the bug on a Windows 10 machine.
I will try on a Windows 8.1 machine, and others, but it will have to wait until next year
It could be hardware/driver-related, as you may know the "interpolated scanlines" option uses hacks.
Do you have more details: PC display resolution, ST display size, etc.

[FedePede04]

i think that i found a way to trigger the interpolated scan lines error, Steven try turning on triple buffing.
if i turn on triple buffing then i don't have any scan lines in windows mode, and in full screen it only show a picture in the upper part of the screen.

[axelfoley]

Thanks for the welcome. And thanks for your Work with steem sse. Keeps better and better every time. Can't wait for 3.8
I can only test in Windows 8.1
2 pc's, one with 32 bit and the other one with 64 bit. Both are equipped with nvidia Cards gtx 285 and gt7600. Latest drivers.
resolution 1920x1080. All other available resolution tested. Same result. Tried every setting possible, with same result.
Hope in 2016 you can reproduce this screen issue.

[axelfoley]

Forgot to mention, this is a widescreen monitor, with st aspect ratio enabled in fullscreen d3d.

[FedePede04]

Hi axelfoley and welcome to the forum.

under the option 'SSE' do you have triple buffing turn on?
if yes please turn it off.

btw. i am also running windows 8.1

[Steven Seagal]

Off topic: my new computer came with Windows 8.1 Pro, I upgraded for free to Windows 10 Pro and was enchanted with the improvements.
YMMV.

[axelfoley]

Hi Steven.
When I toggle always show borders on, fullscreen works with interpolated scanlines enabled.
If I toggle auto borders on, the image hangs low, no borders. - Extended borders ?? Still interpolated scanlines enabled.
Without interpolated scanlines fullscreen works OK. No borders show. Full image.
Maybe it's my knowledge with Atari and borders ??
But the play area without borders are much bigger and better.
Maybe thats how it works.
Maybe with your new pc your can reproduce.

FedePede04. tripple buffering is grey. Not able to select.
Happy new year guys.

[Steven Seagal]

Maybe with your new pc your can reproduce.

Yes indeed I can reproduce the bug now, it's not OS-specific. My routines are confused by 'auto-border'.

Here's the plan: this confusing option will be removed. It will be On or Off, no more Auto.
Also, VSync and Triple Buffering will be enabled no matter the OS.
Still think Triple Buffering is useless since Vista, but I noticed VSync works on my Windows 10 PC.

[axelfoley]

Fantastic Steven.
Thanks.
Happy new year.

[thornburgh]

Very happy to see that you are continuing Steem development. I just discovered that Steem 3.2 couldn't go fullscreen on my new Win10 machine. SSE works great!

However, I did notice one issue: after associating .STS snapshots with SSE in Windows, they no longer open when Steem starts. They do open Steem, but the disk drive is empty. This was not how 3.2 worked.

Double clicking .ST disk images works, however.

Thanks!

[Steven Seagal]

Very happy to see that you are continuing Steem development. I just discovered that Steem 3.2 couldn't go fullscreen on my new Win10 machine. SSE works great!

However, I did notice one issue: after associating .STS snapshots with SSE in Windows, they no longer open when Steem starts. They do open Steem, but the disk drive is empty. This was not how 3.2 worked.

Double clicking .ST disk images works, however.

Thanks!

Welcome to the forum.
You'll be happy to see that this little bug has already been fixed action man-style for next version.
Plz check this thread :

http://www.atari-forum.com/viewtopic.php?f=40&t=28538

[TheNameOfTheGame]

Edit..NVM I forgot to put pasti.dll in the directory

[thornburgh]

Very happy to see that you are continuing Steem development. I just discovered that Steem 3.2 couldn't go fullscreen on my new Win10 machine. SSE works great!

However, I did notice one issue: after associating .STS snapshots with SSE in Windows, they no longer open when Steem starts. They do open Steem, but the disk drive is empty. This was not how 3.2 worked.

Double clicking .ST disk images works, however.

Thanks!

Welcome to the forum.
You'll be happy to see that this little bug has already been fixed action man-style for next version.
Plz check this thread :

http://www.atari-forum.com/viewtopic.php?f=40&t=28538

great, thanks!