forum.defence-force.org

Updates again! Download developer builds HERE ! Tested on real machines under Linux, macOS Mojave 10.14.4, Windows 10 and Android. Short list of changes: -------------------------------------- * Added missing chars (@,&) in monitor font * Fixed typing upper case chars and syms in debugger windo...

Beautiful! I'm really obsessed with Oric's 'dotted' surface .
@ibisum: you can create SD-Card library with down-scaled labels too .

... someone (iss?) iss(!) ;) Use the original source code (attached vsync-auto.zip). Please revise it, I think I didn't update it to the last ThomH's post. I will check it too later, but now I'm in the middle of something ... important ;). Use the test example (attached testvsync.dsk.zip) - pressin...

Very cool game. I like it!
¿Any chance for English translation, por favor?

I've checked and the problem is NOT in new compiler, so no further action required. :) For the sake of completeness only: the issue appears with the newer version of XA - 2.3.9, where the symbol '^' in quoted strings is parsed as CTRL+(next character) i.e.: .asc "^A^B" is assembled as only...

I can confirm that last update in compiler works for me - no more problems with compilation found yet. @Dbug: can you check one of your demos: http://miniserve.defence-force.org/svn/users/dbug/demos/Cube/ It works by me with old compiler, but not with the new one - after 3-4 frames the cube is drawn...

It's trimpot or trimmer potentiometer

Wow, @Godzil welcome back! It's not the RAM - the same test runs for hours without errors when accessing low addresses (i.e. 0000-C000), only if MAP is active then after some period of time fails start to happen. I'm using 74LS123 and the Cext are new and stable tantalum capacitors. But as I said - ...

Dbug wrote: ↑Fri Apr 19, 2019 8:20 amIs that maybe what the Microdisc RV1 is for?

Yes, exactly in Microdisc RV1 does the job.

Annoying RAM Overlay (MAP signal) failure - interesting moments to watch are 00:02:50 and 00:04:40: https://youtu.be/jPme_n0RD-E While Oric #3 is rock solid, after some time Oric #1 and #2 start to give errors when accessing addresses in the enabled RAM Overlay. The explanation is clear - things get...

... and here is how the gray movie was 'sliced' in levels of gray. The mixer is still 'Direct connection' next on the list is the 'R-2R thing' and the audio mixer (I'll draw some schematics for discussion).

OricExos plays B&W animation (4 frames). Every Oric draws 1/4 of the image as horizontal band (240x50 pixels): https://youtu.be/_IKJ8QSKXwQ The source code is not optimized but playback is smooth and flicker-free! OricExos plays Gray scale movie (11 frames). Every Oric draws full image 240x200 ...

Just found a problem. This program: static unsigned char data[] = { 0x80, 0x81, 0x82, 0x83, 0x84, 0x85, 0x86, 0x87, 0x30, 0x31, 0x32, 0x33, 0x34, 0x35, 0x36, 0x37, }; void main(void) { return; } is processed by compiler to: /* 16-bit code V1.34 */ Ltest129 DB($ffffff80) DB($ffffff81) DB($ffffff82) D...

I've updated my Linux toolchain with the new compiler - so far no problems, except one little fix: After update from SVN 'debug.c' file was deleted: D public/pc/tools/osdk/main/compiler/sources/debug.c because the new compiler doesn't need it, but the file name remains in public/pc/tools/osdk/main/c...

... and you can adjust the line: with different coefficient (i.e. 1,10,100...) to 'fit' better the expected result .