P96 3.5.0 fails with Indivision ECS V4

Caution: Non registered users only see threads and messages in the currently selected language, which is determined by their browser. Please create an account and log in to see all content by default. This is a limitation of the forum software.


Please understand that you need to create an account to be able to post, guest posting was disabled as an anti spam measure.

    This is CDTV, with TF536, OS3.9, BB1&2, latest MMU libraries from Aminet.


    Error message is :


    P96: Could not create graphics board content for "IndiECS", please check your 96 installation.


    Native driver works, but IndiECS not. First I made update, then I removed and made first install.


    MuFastRom works, tested with it and without it. Tested with SetPatch NOROMUPDATE, no help.

    Correction, correct error message is :


    P96: Could not create graphics board context for "IndiECS", please check your 96 installation.


    Noticed that there is a FindIndiECSv4 command line tool in program folder, if I run it, it doesn't gave any messages?


    ReInstalled MMU libraries, recreated MMU config file no help.

    Problem solved, solution was firmware update. I didn't though it first, as my Indivision is brand new.


    But seems that it gets "stuck" on screen mode, when press "test" button from PicassoMode or Screenmode window. Only solution to get a rid of it is turn OFF and ON. Reset doesn't fix it. I ques this is already known bug.

    No, it's not a known bug... Did you put the indi into the display chain? ToolType DisplayChain=YES must be set.

    This seems to be a problem restoring the saved configuration. I'm pretty sure that this was discussed during development, and I have considered it a solved problem. Will get back to you when I find a solution (or at least I can reproduce it here).


    On another note, Doom is surprisingly fast on your setup!


    Jens

    Quote from Jens

    On another note, Doom is surprisingly fast on your setup!


    Jens

    When I start IndivisionECSv4-1.0. it tells that "configuration is not saved to device", save and apply solved messed screen problem. Thanks for a hint.


    Generally I'm very pleased to Indivision, no matter that there are still some quirks. I think I'm going to buy another one for my A500.


    ADoom works fine with RTG, but DoomAttack doesn't. It still asks c2p module.

    Hardware: ACA500plus + ACA1233n, IndiV4 reset to default, latest firmware

    OS: clean 3.2.2.1


    After installation, i see only a black screen. (PAL preset)

    RTG works only, if i start the monitor driver manualy after loading the workbench.

    P96Prefs shows no indiECS.

    ADomm is running.

    Switching to PAL to run Sysinfo an back works.


    Running IndivisionECSv4 Tool switch the indi to NTSC preset shows a black screen.


    DisplayChain YES or NO shows no differences.


    At the beginning I had the same problem as utri007.

    But when I switched on the MMU, it was gone.

    You obviously installed the latest core; Does the config tool show "unsaved" settings when you start it? If it does, please do save all settings.


    Quote from rolle

    Running IndivisionECSv4 Tool switch the indi to NTSC preset shows a black screen.

    The Indivision ECS tool will not switch WB to NTSC- Only the Prefs tool "Screenmode" can do that.


    If I'm understanding this wrong, feel free to open a thread in the German part of the forum - I know you're native German.


    Jens

    Generally most of RTG games work. Here few problematics games.


    DoomAttack doesn't understand it is RTG mode, it requires choose c2p module.

    Gloom Deluxe/SE versions doesn't start, gives guru.

    OnEscapee starts but player character is invisible.


    Genetic Species plays very well https://youtu.be/xHkC7wcLn-U

    Quote from Jens

    Do those problematic games even support RTG screens?


    Jens

    Here short demonstration of problem. All Amigas has same version of P96.


    https://youtu.be/hY3nT-GC3NE


    Note Gloom SE work in ehb 64 colors ECS screen. All Gloom versions does crash if runned RTG screen with Indivision.


    OnEscapee has mutiple problems with Indivision ECS RTG driver. Start demo doesn't display at all, but displays with too other Amigas with same p96 version and two different graphics card. Actual game play doesn't work, that is with all three Amigas. I'm pretty sure that it has worked earlier. Game is PD if some one wants to look. https://amiga.abime.net/games/view/onescapee

    Quote from utri007

    All Gloom versions does crash if runned RTG screen with Indivision.

    Please contact the Gloom authoprs and point them to the latest developer archive. As noted years ago, some things have changed.


    Will take a look at the other games when we're testing the Blitter implementation. Keep bug reports coming!


    Jens

    Hi,
    I had a similar issue to utri007 where the indiECS was just grayed out and I got the same error message "P96: Could not create graphics board content for "IndiECS"".

    So I tried what utri007 suggested and performed a firmware update with the rescue disk.

    Now I can select the IndiECS in 96 but when trying to use the Indy Config Tool to adjust the screen mode I got a black screen.

    I assume it might be related to the fact that the rescue disk you offer is older than the latest firmware. Can I just copy the latest firmware onto the rescue disk and update it like that?


    Cheers,


    Thomas

    Quote from Lokiist

    I assume it might be related to the fact that the rescue disk you offer is older than the latest firmware.

    Correct - the latest firmware contains all the required updates to the framebuffer mode, but that's not contained in the rescue disk.


    Quote from Lokiist

    Can I just copy the latest firmware onto the rescue disk and update it like that?

    That's one possibility, but I'd suggest to use the configtool and the menu item from the drop-down menu that says "flash firmware" (or similar). No reboot required.


    Jens

    Hi Jens,


    I managed to use the configuration tool to update to the latest firmware you offer.

    But I still have the issue not being able to use the configuration tool when using an RTG Screen like 800x600 0r 1024x768 so I can adjust those.


    Cheers,


    Thomas

    One additional question, is the latest available firmware "baked in" to the configuration tool or is the separate one on the website newer?


    Cheers,


    Thomas

    Quote from Lokiist

    But I still have the issue not being able to use the configuration tool when using an RTG Screen like 800x600 0r 1024x768 so I can adjust those.

    That's expected, as the config tool is only for flicker fixer operation. Anything RTG-related is handled by P96. Running the config tool on an RTG screen is currently not inhibited, but will be in the future.



    Quote from Lokiist

    One additional question, is the latest available firmware "baked in" to the configuration tool or is the separate one on the website newer?

    The separate one is newer. It's not in a state where it's fit for being rolled out officially. Too many things "in flow".


    Jens

    Good News, I finally got it to work and I have to say so far I am quite happy with the results!

    I even managed to get it usable in 1024*768 with 256 Colors using the ACA1234/ 25Mhz.

    Now this Rev8a Amiga 500 is loaded with iComp expansions(ACA500Plus,X+Surf500, ACA1234, A2048,indiECSv4 and a CA-PSU) 8) .


    One thing though when using any RTG Screenmode my boot up time take much longer(we are talking about like at least 5 Minutes) I did some troubleshooting tracing the boot process and as expected it hangs at "LoadMonDrvs".

    Is that something that you guys already are aware of?


    Cheers,


    Thomas