| |
Mirage
Registered: Jan 2003
Posts: 113 |
Release id #30789 : Timanthes
Starting a new thread so i can answer any questions about the program without polluting the comments thread.
I've already added some trivia-notes about it being a beta version, and not everything working properly yet, but it should be enough for people who just want to make koala/fli/afli/hires pictures :)
So, bring on the complaints :) |
|
... 57 posts hidden. Click here to view all posts....
|
| |
Copyfault
Registered: Dec 2001
Posts: 478 |
Hmm, does not seem to be really stable :/ I managed to save some AFLI-data (still have to check the output), but just as I thought I understood how Timanthes wants the layers to be set... I failed :(( I was not able to recreate a setting that allows me to export to a C64-file. And I really followed your advice, Mirage...
Maybe my version is not ok...
...how long do we have to wait for "an update" ;) ? |
| |
Mirage
Registered: Jan 2003
Posts: 113 |
It's really not that difficult, you just have to make sure the layer with the bitmap data is always the second layer... what ever restriction mode you want to use.
And about the not being stable: i fixed the GDI+ bug about two weeks ago (this was the bug that was crashing the program 8 out of 10 times) and i'm cleaning up some more before I put out beta 2 which will be a LOT more stable and user-friendly. |
| |
Copyfault
Registered: Dec 2001
Posts: 478 |
Nice to hear about a new beta coming up *freu* Will this one already include code fragments of viewers for the c64 as mentioned some days/weeks ago?
Speaking of viewers: a really nice feature would be a "code layer", giving some kind of interface to the cycles within every rasterline. I am thinking of a grid consisting of 63x312 cells (maybe less, as not every rasterline is necessarily concerned with gfx) where it should be possible to assign opcodes to the cells. Thus, not only custom values for x-shift in every line would be possible (as Krill suggested), but also the other VIC-regs could be changed (open sideborder etc.) Most probably this is far to complicated to do - can't tell, as I never did any paint.net-stuff nor other serious projects on PC.
Just wanted to share my ideas which came up when using Timanthes...
CF |
| |
Mirage
Registered: Jan 2003
Posts: 113 |
Somebody asked me how FLI was exported today on IRC (Quasar?) but left before i could answer... here it is:
FLI:
----
'FLIgraph2.2/Black Mail' editor format
$3b00-$3c00 - $d021/opcode colours
$3c00-$4000 - colourmem ($d800)
$4000-$6000 - charmem
$6000-$8000 - bitmap
the $3b00 bytes are built up like this:
lownybble - $d021 colours
highnybble - opcode colours
opcode colours are used to colour the extra colour in the 3 char-fli-bug area on the left... (most FLI pictures don't use this and it's too technical to explain here, anyway :))
Hope this helps other people aswell |
| |
QuasaR
Registered: Dec 2001
Posts: 145 |
Yes, was me, thx!! Helps me a lot, since AAY64 seems to have some bugs left there (poking Ninjas lazy ass... ;) ) |
| |
Oswald
Registered: Apr 2002
Posts: 5094 |
char mem aka screen mem :)
btw opcode color goes into d800 pixels ? |
| |
JackAsser
Registered: Jun 2002
Posts: 2014 |
@oswald: The $d800 color of the FLI-bug area is indeed controlled by the opcode following directly after the $d011 write. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11386 |
mmmh trying to make this work in wine, and as often, the msi installer thingy craps out... could you add a plain "standalone" version too ? |
| |
JackAsser
Registered: Jun 2002
Posts: 2014 |
@gp: when u get it to work, tell me how u did it plz. Same goes for Grahams' warpcopy... (not that he uses msi, but the app is stubborn anyways) |
| |
A Life in Hell
Account closed
Registered: May 2002
Posts: 204 |
Quote: @gp: when u get it to work, tell me how u did it plz. Same goes for Grahams' warpcopy... (not that he uses msi, but the app is stubborn anyways)
warpcopy has just worked in wine for over a year now, for me (i just apt-get install wine on ym laptop, and run wine ./warpcopy.exe) with one caveat: the squares in the track/sector display are not squares, but dots. But no matter.
Neither Timanthes or P1 work for me though... have to vmware to run those - P1 is close, though, and I actually know _why_ that fails and how to fix it. I may yet patch wine after I get some free time.
EDIT: the big thing with warpcopy, is it uses directx for the display, and so you need to make sure that you don't have an old wine config around where you set desktop depth to something other than display depth, because that will break warpcopy
--j |
| Previous - 1 | 2 | 3 | 4 | 5 | 6 | 7 - Next |
