Infinity Modules Player for all CPU & OS

[Michael]

New issues, tried on a new 3.2 install with Pi96, and there it freezes immediately on start when can't find the fonts (partial GUI drawn)

Tried on a new 3.9 install, AGA, and that fails too, but fully crashes and outputs random gfx pixels to screen (like no analogue TV signal).

So some fail safe checks are missing to prevent dead ends.

[juen]

Originally Posted by Michael

New issues, tried on a new 3.2 install with Pi96, and there it freezes immediately on start when can't find the fonts (partial GUI drawn)

Tried on a new 3.9 install, AGA, and that fails too, but fully crashes and outputs random gfx pixels to screen (like no analogue TV signal).

So some fail safe checks are missing to prevent dead ends.

there is no way to not find fonts (default fonts are included in main .exe)

still working nice for me on OS 3.2.1 RTG P96 (Warp1260)

gfx glitches could be because of that what I mentioned before - "after the update there may be an error, it is already fixed but unfortunately this one time may still occur"

also working nice on AGA, and tested now on A2000 ECS with 030.

No one else reported any issues, and there was a few ppl online since morning update. Please check what else can make errors on your machine.

when reporting "errors", please also report your full configuration (amiga type)

[Michael]

I have tried mostly A1200/3.1 3.2 3.2.1roms
WinUAE 4.3 4.5 4.9 030/FPU FULL EMU JIT with extra ram 2MB+4MB+128MB

Nothing special.

The font problem could be related to the saved prefs file and missing font. The internal one does show up in custom screen windows just before all dies.

I have not investigated much as to what might be the cause of other problems yet,
but given that most other things work reliably I suspect something unfriendly happening here.

Running imp3 in MMU debug environment is not so friendly, a lot of word read hits from zero
and dos.lib call problems...

[juen]

Originally Posted by Michael

Running imp3 in MMU debug environment is not so friendly, a lot of word read hits from zero
and dos.lib call problems...

huh what, why? I am using enforcer, just checked again and don't get any hits! can u provide screenshot with logs and imp3 from the moment of hit?

[juen]

ok, got info on pm from Michael, there maybe possible errors where starting from icon so....

imp 3.365

- possible errors detected by enforcer in startup code when starting from error fixed (?)
- detecting FPU (and 68LCxxx)
- much bigger buffer when available for disk/stash (even 4000 rows!)
- own screen now id using selected fonts
- border bottom with size gadget size detecting fix
- listview click vs position fix
- and some bug fixes

[Michael]

Yes! That's much better, and even the gui is good in custom screen.

Now, running the game is still a problem, don't get to see the screen first time, and also on exit [ESC] you get this, then you get this on every start, and the game is shown ok, but we do also get a popup window with imp console and ESC key presses are registered there causing WB to go upfront.

26-Dec-21    12:44:46
WORD READ from 00000000                        PC: 404A53E8
USP : 404ABEF8 SR: 0008  (U0)(-)(-)  TCB: 404A17A0
Data: 00008212 0000FFFF 0000FFFF 0003AEE8 0000FFFF 0000FFFF 00000008 00000000
Addr: 00000000 000222F4 00043AE8 00043AEC 404A9FB6 00020EDE 404AA1B8 400022DC
Stck: 404A46DE 00F9E266 00001000 404A2654 404BD7D8 00008690 00000000 00000000
Stck: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Stck: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Stck: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
----> 404A53E8 - "ram:imp.tmp"  Hunk 0000 Offset 000012B8
----> 404A46DE - "ram:imp.tmp"  Hunk 0000 Offset 000005AE
----> 00F9E266 - "ROM - dos 47.30 (2.12.2021)"  Hunk 0000 Offset 00000AD6
PC-8: 23FC0003 C2E8404A 97364E75 2039404A 970ED079 404A9706 DBC02079 404A959C
PC *: 4A506600 005A0839 000600DF F0020839 000600DF F00266F6 23F9404A 973200DF
404a53c8 :  23fc 0003 c2e8 404a 9736   move.l #$3c2e8,$404a9736
404a53d2 :  4e75                       rts
404a53d4 :  2039 404a 970e             move.l $404a970e,d0
404a53da :  d079 404a 9706             add.w $404a9706,d0
404a53e0 :  dbc0                       adda.l d0,a5
404a53e2 :  2079 404a 959c             movea.l $404a959c,a0
404a53e8 : *4a50                       tst.w (a0)
404a53ea :  6600 005a                  bne $404a5446
404a53ee :  0839 0006 00df f002        btst #$6,$dff002
404a53f6 :  0839 0006 00df f002        btst #$6,$dff002
404a53fe :  66f6                       bne.s $404a53f6
404a5400 :  23f9 404a 9732 00df f050   move.l $404a9732,$dff050
Name: "Background CLI"  CLI: "ram:imp.tmp"  Hunk 0000 Offset 000012B8

[juen]

but i don't have any problems with whdload on any my amiga...

my current setups for testing imp:

a4k with zz9k and 060 + roadshow
a2k with tf536 and matze lan + miami
a1200 width pcmcia lan warp 1260 + roadshow
a500 with aca500+ and aca1233n with xsurf + amtcp
cdtv with plipbox + roadshow

this code showed in log from enforcer here is not from imp directly (i think this is one of executed commands (whdload maybe?) in this background cli)

window is output for executing scripts (network disabling/enabling)/lha/whdload etc...

as you see this is code from whdload or whdload game for 100%, this code means:

;A correct blit wait, compatible with all Amigas:
tst.w $dff002 ;required for code running in fastram on the first A1000 models
.wait: btst #6,$dff002
bne.s .wait
;--- set up the next blit here ---

so this is not imp3 related problem but maybe something with your setup

[Michael]

I agree, it has little to do with the main program, it's the game that has problems bringing the screen to front. Even when run as a separate standalone exe it does the same, can show the screen or not and keep you locked out.

Also when you quit the game by ESC when you had luck to get it runnng from IMP then WB opens this window

[juen]

Originally Posted by Michael

I agree, it has little to do with the main program, it's the game that has problems bringing the screen to front. Even when run as a separate standalone exe it does the same, can show the screen or not and keep you locked out.

Also when you quit the game by ESC when you had luck to get it runnng from IMP then WB opens this window

yep as i said this window is output window for executing scripts. for example after running whdload game imp will use own script to bring back network (network is disabled before launching whdload).

this window should be auto closed after end of script

[juen]

Originally Posted by Michael

I agree, it has little to do with the main program, it's the game that has problems bringing the screen to front. Even when run as a separate standalone exe it does the same, can show the screen or not and keep you locked out.

Also when you quit the game by ESC when you had luck to get it runnng from IMP then WB opens this window

yep as i said this window is output window for executing scripts. for example after running whdload game imp will use own script to bring back network (network is disabled before launching whdload).

this window should be auto closed after end of script (while it is open you can find this temporary scripts in ram

ps: i see there ] (esc), try to delete it - maybe this is blocking script

[Michael]

Yes, it blocks, and deleting makes it move forward, but it is so annoying that esc gets caught. And how it gets there if focus should be on the game screen, or back to wb/custom screen, so hidden cl should not get the input unless the game somehow does not swallow it and passes over the shell it was run from.

Also you are not running the game via whdload or parts of it are included in the game code? WHD is fairly good at switching the system on/off.

Also the game sometimes crashes for no reason into the garbled graphics (happens after playing a few times) you make a move, and boom.

[juen]

Originally Posted by Michael

Yes, it blocks, and deleting makes it move forward, but it is so annoying that esc gets caught. And how it gets there if focus should be on the game screen, or back to wb/custom screen, so hidden cl should not get the input unless the game somehow does not swallow it and passes over the shell it was run from.

Also you are not running the game via whdload or parts of it are included in the game code? WHD is fairly good at switching the system on/off.

Also the game sometimes crashes for no reason into the garbled graphics (happens after playing a few times) you make a move, and boom.

this is still not problem of imp, but fault of whdload or your setup.

i don't know why you are hitting escape when whdload is no more running :-) of course self whdload should remove from buffer hitted escape and don't throw it to your system. but I don't know how I can help you. everything is working fine for me and other users...

"WHD is fairly good at switching the system on/off"

nope. how? and not system - networking! most of games and demos will not work until network is switched off, this is common issue of whdload. u still need to have selfwrited scripts in S: for that :-) imp does not require you to do this, nor does it require whdload on your system

"Also the game sometimes crashes for no reason into the garbled graphics (happens after playing a few times) you make a move, and boom."

maybe there is still network connection, I dunno. you need to figure it out

[juen]

imp 3.366



wip: stats window

[juen]

imp 3.367

first attempt to quick tools panel

[Michael]

Small gfx problems...
- sliders going out of bounds
- text wrapping/window size have large empty areas



The issue regarding running game on P96/RTG system is trivial.
The game locks out the system before the system has a chance to switch displays. The work around is to press END+F9 to force switch. The same may be required on quiting, since first you have to close the dummy con window that catches ESC, then return to black game screen, and then it will shutdown.
This is apparently because the game switches the system too fast without waiting for vbl an not allowing the system to do it's job.

[juen]

Originally Posted by Michael

Small gfx problems...
- sliders going out of bounds
- text wrapping/window size have large empty areas



The issue regarding running game on P96/RTG system is trivial.
The game locks out the system before the system has a chance to switch displays. The work around is to press END+F9 to force switch. The same may be required on quiting, since first you have to close the dummy con window that catches ESC, then return to black game screen, and then it will shutdown.
This is apparently because the game switches the system too fast without waiting for vbl an not allowing the system to do it's job.

"- sliders going out of bounds"

this is natural because I have added one button here, just resize your window once and the problem will be fixed

listview is always word-aligned, so not even characters was moved to next lines. I am supporting all CPU, so this is for mc68000, and speed/optimizations. just resize your windows to fit them all nicely

"since first you have to close the dummy con window that catches ESC"

I think there is a problem with your system, some weird patched? this window opens by itself and CLOSES itself ALWAYS!

and it should not catch any ESC, but I wrote earlier that you put it there yourself

[Predseda]

I have blown sound output from my Amiga so I can not enjoy IMP music at this moment

Untill it is repaired or I set up another machine, I will be able at least use chat. Looking forward to check the new version, though.

[Michael]

Originally Posted by juen

"- sliders going out of bounds"

this is natural because I have added one button here, just resize your window once and the problem will be fixed

Yes, that kind of fixed it, dose not happen now.

listview is always word-aligned, so not even characters was moved to next lines. I am supporting all CPU, so this is for mc68000, and speed/optimizations. just resize your windows to fit them all nicely

Yes, and the window dimensions are sticky to some form of grid based on the font in use, sadly you can't resize the window and have no empty space, it is always fixed to some odd dimensions that will not compute to bordertop+borderbottom+fontlines=windowsize

"since first you have to close the dummy con window that catches ESC"

I think there is a problem with your system, some weird patched? this window opens by itself and CLOSES itself ALWAYS
and it should not catch any ESC, but I wrote earlier that you put it there yourself

It does auto close itself once you delete the chars you pressed and got there somehow, the question is why the get there in the first place and why does it open to start with, the game should run without opening a visual cli. This could also be related to P96 screen switching issue since the system can not detect the changes and could keep the focus on the wrong window/screen, and new windows get autofocus by default. Ideally the game should wait 2 vbls after opening it's screen and only then take over the system.

[juen]

"
Yes, and the window dimensions are sticky to some form of grid based on the font in use, sadly you can't resize the window and have no empty space, it is always fixed to some odd dimensions that will not compute to bordertop+borderbottom+fontlines=windowsize"

try harder, I think this is possible

"It does auto close itself once you delete the chars you pressed and got there somehow, the question is why the get there in the first place and why does it open to start with, the game should run without opening a visual cli. This could also be related to P96 screen switching issue since the system can not detect the changes and could keep the focus on the wrong window/screen, and new windows get autofocus by default. Ideally the game should wait 2 vbls after opening it's screen and only then take over the system."

this is my window, it is opened before starting whdload and closed after end of whdload. this window is providing output for the system exec function "execute". this is nothing abnormal (just like executing a command from workbench menubar). new windows are only focused by default when is ACTIVE WINDOW flag set. i think You have some patches to change that behavior. I could add a 2-second pause if that is to get things done, but only I can do it if at least a few users have this problem (because of unnecessary delay). as long as it is only with you, you need to look for a solution. for me, the picasso works, both on v2 and warp and zz9000 ... on 3 different computers

[Michael]

I have tried, it does not work, it jumps in sizes, either smaller or larger, but not to the font+window dimensions

No need for 2 secs delay, only 2 screen refreshes should be enough for PicassoIV board to switch outputs when P96 signals it.