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.
Also users that are not logged in can not create new threads. This is a, unfortunately needed, counter measure against spam. Please create an account and log in to start new threads.
Did somebody rub my lamp?
The restore key is on the chameleon_io entity and is available in docking-station mode, the signal is called "restore_key_n". In cartridge mode you indeed need to observe the NMI signal (and hope the user hits the key rather hard ;-).
please don't think this message is in any way an "I want a pony! Now!" demand
Sorry, I've checked the shop system, but we out of stock on those. Only Animal avaiable at the moment is a Chameleon.
At present enabling VSync (with the VSync line set to default value 100) or Auto Resolution causes the picture to disappear completely on all of the TVs I have available to test. The TVs report that the signal goes out of range as soon as either are enabled. Changing the Vsync line value does not seem to change this behaviour.
The vsync line can be used to move away a bit of tearing if it would occur at the bottom of top edge of the screen. Changing this value won't help if vsync doesn't display anything at all. Did you try auto resolution at Super-hires mode? On my TV here auto-resolution only gives a picture if I set the mode to sample at super-hires (even for hires or lowres pictures). The 28.x pixel clock is too low for the TV to accept, but at super-hires auto-resolution outputs 56 Mhz pixel clock and TV is fine with that.
Lastly, when I put the Mk3 into 1080p 50Hz and play a game with scrolling, I can see a screen tear ripple about every 10-12 seconds, and I can also see on the Mk3 OSD that it thinks the Amiga’s screen refresh rate is fluctuating between 50-51Hz. I don’t know if this is normal, so I thought I’d let you know in case it’s relevant to any of the above.
Yes that 50, 51Hz is normal, it counts the number of frames it sees in 1 second for display. It is for user information only the value isn't used to make any decisions. A more accurate way to measure these low frequencies would be to determine the time duration of a frame and take the reciprocal (1/x). However dividing is kinda hard to do in hardware so just accept the +/- 1 error please 
Display MoreFor some reason i cant get vsync over HDMI ok.
I do get image, but it looks like an interlaced mode on a 1084 monitor. Its like the screen is moving a bit down by half a pixel and then normalize.
I got this result with try and error, but also by using the values from an online calculator. With vsync off, the image is 100% ok with these settings. Tried this with 3 televisions and 4 freesync gaming monitors, all have the same result.
Does anybody have this working, maybe you can share the settings used?
Did you try it with "auto resolution" enabled? As just vsync has the problem that the VGA/HDMI output and the Amiga input will not contain the same number of total pixels. So there is a jumpy line at the bottom of the screen, which might confuse the HDMI input on the monitor. With auto-resolution enabled the output is forced to have the exact same number of pixels and lines (or twice that) as the Amiga input. Although it will limit the choice of output resolution and for some monitors it only works when setting the mode to SuperHires (even though the games are hires). As this will force a doubling of the Amiga pixel clock as bases for the HDMI. The default 28.x Mhz is often too low for HDMI/DVI monitors (but often works on VGA). But when it works it gives a very good vsync result.
I use a CyberVision for my workbench mode - so just want to get the games looking sweet .. my native resolution is 1280x1024 and is a BENQ BL912. The EDID stuff .. when I ask it to get the values from the monitor it completely fails and gets nothing.
Just a random question. Have you daisy chained the AGA mk3 through the CyberVision or does it have a separate cable to the monitor?
Oh I believe you, sometimes it is the simple things! I'm glad you found the problem.
HDMI does send more data during the blanking period compared with DVI. So yes it could result in different behavior.
Anyway - I did somehow 'fluke' a view that looked pretty good on the monitor but some games just seemed to view too large for the screen resulting in losing a bit of the top (Alien breed 2), or the right (Ruff n Tumble).. Others had similar problems. Using the config tool I'm not sure how I would fix this as the 'adjust mode' is for the indi mode not the game mode? (or am I wrong here).. I couldn't find a way to adjust it and going into vga settings is not the same ability to move the screen around?
There isn't a "indi mode" as such (you can select what screen mode to use for adjusting or testing, but normally you want to test with the screenmode that was used to define a config slot).
On the right side in the config tool is a list of config "slots" with names (anything starting with PRE are preset defaults from the software). Most games run in either standard PAL or standard NTSC mode (640x256 or 640x200). So you will need to find the correct slot in the list and select it you can copy a pre mode if you want to change it. Then when you press the adjust button to change things and here you can move the image around. There can be multiple slots for PAL and you can disable or enable individual slots. The AGA mk3 will use the first "matching" slot when the game starts. This is matching is based on the number of scanlines. Copied slots are put at the top of the list, so if you modified a "preset" it will be selected for the game.
I don't have the keyboard connector on as I use a sub1200 keyboard adapter - I know with this on I can scale and move the screen around - but I believe it doesn't remember? what good is that?
The OSD will show the values which you can use in the config tool later. The idea is that the config tool should be able to retrieve the last value set that way as well after leaving the game (not sure if that works already version 1.4). But you can always write the values down it is only 4 of them.
Once it moaned it couldn't find the card and resulted in me painfully pulling my tower apart.
Also save or use will sometimes hang and results in a need to reboot.
Well at least you have a tower. My setup is just a bare 1200 mainboard I got from random box in Jens his basement. Listen, I understand the frustration, but the config tool isn't that buggy for me (and never was even during development). So there must be some library or component in your system that doesn't play nice with the config tool for some reason.
One part (although I'm guessing here) is that you are trying to change the VGA/monitor mode settings to shift the picture or have not selected the correct slot. As the normal adjust screen should not cause you to have to use the rescue disk, but messing with the VGA settings might.
any positive feedback with MK3, everything i read pas few days is problems, errors and Jens and his team doing magnificient job on updates, but what works, how it works, im awaiting my mk3 and im starting to loosing hope that all will works fine.
Hmm, yeah of course that is a bit in the nature of a support forum. You will mostly see posts from people with questions or problems. Especially true for a product that is very new.
Yes the DVI encoder chip gets warm/hot and you can feel that through the PCB. No, you should not be too concerned about that.
The only explanation I have for this is that the keyboard "sniffer" is causing this. In order to catch key presses without the OS running (which is the case for most games and demos), the "acknowledge" signal is sent by the flicker fixer instead of the CPU. This *may* happen, resulting in Battle Squadron believing that the joystick button has been released, where in fact it has been pressed all the time.
Maybe we can implement a temporary "disable" for the keyboard sniffer. I'll talk to Peter.
No current core doesn't send an keyboard ack itself. So that is not it.
Even if I want to use the Indivision with HDMI, someone has suggested me to try VGA output just to see what happens, and also a different HDMI cable (they can be picky), but I must say that the one I'm using I've used it before with the same monitor and a MBP without a single hickup. Also, I'll reset the monitor to its factory default settings, let's see if that makes any difference.
It is not the HDMI cable, a cable issue will result in either a black screen or random color blocks or something digital noise like that. You clearly have a stable picture. The monitor just decides cropping parts of it (for some mysterious reason).
And as for the Amiga screenmode, Super72 800x600, in fact it IS listed as one of the PRE modes in the Indi Setup tool, and that was my first try, both PRE 800x600, screenmode and Indi VGA. Since it didn't work with PRE modes, I made a custom Indi VGA mode and a new screenmode, injecting the screenmode from the requester, in the hope it would be recognized, but no luck either.
Is is enabled? You can enable and disable individual slots. Also PAL might be earlier in the list and if it matches as well (search is based on the number of scanlines the Amiga generates) it doesn't matter what slots comes after it. Changing the order of the slots can help with that. Or you can go the live-edit mode and press 'X' to cycle through all compatible slots for the current screenmode.
Try to use or create a VGA mode in the config tool that matches the native resolution of your monitor (1920 by 1200 probably). Doesn't matter what the Amiga screen resolution is. Your monitor clearly wants a HDMI signal that matches its native resolution. And I'm sure it is a fine monitor for 15khz, but that is not the problem we are trying to solve here. So again try to select a VGA mode that matches the native resolution of your monitor.
in this case, I have found no way to make the screemode to pick the correct VGA Indivision mode: as you can see, even if the test screen says it is displaying Super72: Super Hires Laced 800x600x5 screen, the Indivision logo says PAL 800x600 screenmode over a preset 800x600 VGA mode:
Seems there is no matching slot for Super72. So it picks the standard PAL one instead. That won't work as the Super72 uses super-hires (while PAL is hires) and so you lose 1/2 of the pixels on the Amiga screen. You can't select VGA modes using the Amiga screenmodes directly. With the config tool you assign a VGA mode to a slot(s) that match the Amiga screen mode(s) you want to use. So it is a two step process. First select the VGA modes that your monitor support and assign them to config/mode slots in the AGA mk3 config tool. Then you can select your Amiga screenmode.
But before you try a thousand and one different workbench screenmodes, first make sure you find a VGA/VESA/whatever mode that the monitor doesn't cut off. Then assign that to the various config/mode slots. As your monitor seems to be a bit brain-dead in handling VESA modes you can use the scaler in the AGA mk3 to resize the picture to make it fullscreen (or correct aspect ratio with some black bars whatever you prefer).
Display MoreTaking the data from my monitor manual and the resolutions it handles, I have also tried to create two custom VGA modes in the Indivision setup application, one for the HighGFX 1024x768 screenmode:
https://i.imgur.com/hnJhpWh.jpg
The only thing I have not tried is to disable the "PRE Pal: 800x600" mode in the Indivision Setup application.
As you can see, it's not that I have not tried different things, but as I am new to Indivision, maybe there's something I'm overlooking?
What do you think? Any help will be appreciated.
Yeah so you tried 800x600 and 1024x768 both modes not native for the display resolution. Changing the Amiga screen modes will not help if they are mapped to the same VESA mode. You could try finding an "auto adjust" or something named like that in the menu of your monitor. But if it cuts off that much by default wouldn't really trust that will help.
My suggestion is trying one of the detected EDID modes that match the native resolution of the panel (1920x1200@60 if I interpret the attached pictures correctly). Or you could try 1080p for HDMI/DVI as that is listed as supported in the documentation page you posted.
btw. is there any changes or the speed of changing gfx mode LACE/PAL
for example some games like Alien Breed, Agony and many demos have some graphics displayed in Lace and the rest in PAL in MK2cr is a slight delay when switching from one to another.
Could you write something more about it?
With the AGA mk3 (like it is in ECS v2) you will be able to share a single mode for both PAL interlace and normal PAL by setting the "double line" option. By default it will double the number of lines on the screen to keep the aspect ratio, but on interlace this line doubling is automatically turned off. So your monitor doesn't have to switch to a different screen resolution and it should be almost instant (like 3 half frames or so). I don't remember exactly what the MK2cr does with interlace, probably load a different image from flash or something, which will take a while yes.
by the way, not once talking to friends we wondered why Graffiti was in IndiECS and it was not in MK2cr.
Don't know. I didn't work at icomp at that time, so wasn't involved with creating the specifications for that product. I guess it was on a similar "nice to have list", but never made it into the product. Note: Although I did implement part of the firmware for the AGA mk2, it was in the role as an external consultant.
Display MoreHello, I have finally registered: P
Thanks for answering but for me it looks like withdrawing from what you previously confirmed, and I am sorry but I am not buying this statement that you confused Graffiti with another function.
We are how many months one or two before the market debut of MK3 and a bit of a shame that we do not know the full specification and available undisclosed functions.
I am very pleased with the MK2cr I have, and as for the new version, I have certain expectations. Grafitti is one of them.
Now, I must admit that I have to think about what to do with the MK3 preorder.
Thx for info and stay safe for all of you.
The reason we don't tell the every feature that is on our todo or planned feature lists, is because there could be technical or planning reasons these features are left out at the last moment, or are delivered in a later firmware update once they are properly debugged. Better to only communicate what we know for sure will work, to prevent any disappointment for our customers.
Now for Graffiti, it didn't make it to the "for sure" list for some reason, I just thought it did. As aga mk3 is based in large part on the ECS v2 design and that already has Graffiti emulation, so that code was already existing only color depth has been extended from 12 to 18 bits. I already did all that work so that is why I communicated it will be in, not realizing Jens didn't have that confirmed yet. Not sure why though will ask him when he is back from holiday. With all the crazyness in the world at the moment some communication errors are bound to happen. Sorry to see some of that leaked out into this forum.
Best advice I can give you for your pre-order is read the shop description, that is the product you get for sure.
Now Jens wrote
"It's currently on the "nice to have"-list, but not on the "promised to be in"-list"
It is a BIG diffrence maybe its time for full spec of MK3
Ok yes, it would be "nice to have" a purpose for the file named indi_aga_mk3_graffiti.vhd that exists in my firmware development directory. That poor little file, not (yet) promised to exist. Ready to spring into 18-bit action when it is promoted to the other list. I'm sure that will happen once we have the mandatory features stable. Until then just assume I didn't say anything... promised nothing... I was just confused about the Question, yes that is it! I thought you meant a totally other feature with a different name that is on the promised list... yes.. well good that we talked that through, almost slipped a non-existing feature right here in the forum.... whew..
In my A1200 i have a KA 47 Angle IDE 44 PIN with SD Adapter. Will this be in the way for the Indi MK3?
If it looks similar to this picture. Then the answer is no, it is not in the way and you can mount an indi AGA MK3 (or mk2 as is the case in the pic) in the machine at the same time.
Nice! Will Graffiti work with HighGFX driver? I mean, will it be possible to use 720p resolution with Graffiti color support?
I don't know. Depends on the how the application(s) that uses the Graffiti mode will set up the screen. If the application supports 720p I see no reason why it wouldn't work.
is Mk3 have Graffiti support like first ECS had ?
for example for" ADoom, DoomAttack, Nemac IV, ShapeShifter
Yes Graffiti emulation will be supported on the mk3 with full 18 bit color support. (some of the ECS flicker-fixers only do 12 bit color)
I haven't fully analyzed the complete change-log yet (will do that when we prepare the actual release), but what I can see in a quick glance in the list, is a fix for ANE/LAX illegal opcodes, REU timing fixes, some minor cartridge emulation fixes, a bunch of VIC-II fixes related to dma-delay. And the major change will be the new SID emulation code that has been developed that should offer better combined waveforms and emulates various quirks of the envelope generators correctly.
