Log inRegister an accountBrowse CSDbHelp & documentationFacts & StatisticsThe forumsAvailable RSS-feeds on CSDbSupport CSDb Commodore 64 Scene Database
You are not logged in - nap
CSDb User Forums


Forums > CSDb Entries > Release id #30789 : Timanthes
2006-03-27 20:16
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....
 
2006-04-18 16:13
Twoflower

Registered: Jan 2002
Posts: 434
Add background layer, make it backgroundcolor. Add transparency to the color in the second layer, as usual. Or just save it out as .png and run it through Congo.
2006-04-18 17:03
Copyfault

Registered: Dec 2001
Posts: 474
I tried it that way (2nd layer, filled with bgr_col, recolored the other layer (bgr -> transparent col)). As soon as I want to save it to a prg-file, Timanthes tells me something about "incorrect layer settings for c64 export" or so :/ Seems clear to me, as there is no background-colour-info in hires mode...
but how can the layers be set up "hires-mode-friendly" ?

Maybe saving to .png-format an then using Congo is a good idea! Thanks!


CF
2006-04-18 17:46
Mirage

Registered: Jan 2003
Posts: 113
Quote: Add background layer, make it backgroundcolor. Add transparency to the color in the second layer, as usual. Or just save it out as .png and run it through Congo.

No... the proper setup is 2 layers with the following settings;

- 1st layer (can be anything, even non-restricted)
- 2nd layer with restriction AFLI or hires singlecolor
(don't make anything transparent, that's impossible in those modes anyway)

(i.e. you won't see anything of the first layer after you've switched on hires-sc/AFLI restrictions)

Timanthes only exports data that is in the second layer, so it needs a first layer (even if the restriction mode doesn't really need one)

Hope that helps you keep clear from using congo ;P
2006-04-19 09:26
Copyfault

Registered: Dec 2001
Posts: 474
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" ;) ?
2006-04-19 18:50
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.
2006-04-20 10:20
Copyfault

Registered: Dec 2001
Posts: 474
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
2006-05-17 22:08
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
2006-05-17 22:44
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... ;) )
2006-05-17 23:38
Oswald

Registered: Apr 2002
Posts: 5086
char mem aka screen mem :)

btw opcode color goes into d800 pixels ?
2006-05-18 08:44
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.
Previous - 1 | 2 | 3 | 4 | 5 | 6 | 7 - Next
RefreshSubscribe to this thread:

You need to be logged in to post in the forum.

Search the forum:
Search   for   in  
All times are CET.
Search CSDb
Advanced
Users Online
junkie/extend & doom..
zscs
anonym/padua
Jazzcat/Onslaught
Guests online: 138
Top Demos
1 Next Level  (9.7)
2 13:37  (9.7)
3 Coma Light 13  (9.7)
4 Edge of Disgrace  (9.6)
5 Mojo  (9.6)
6 Uncensored  (9.6)
7 Wonderland XIV  (9.6)
8 Comaland 100%  (9.6)
9 No Bounds  (9.6)
10 Christmas Megademo  (9.5)
Top onefile Demos
1 Layers  (9.6)
2 Party Elk 2  (9.6)
3 Cubic Dream  (9.6)
4 Copper Booze  (9.6)
5 Libertongo  (9.5)
6 Rainbow Connection  (9.5)
7 Onscreen 5k  (9.5)
8 Morph  (9.5)
9 Dawnfall V1.1  (9.5)
10 It's More Fun to Com..  (9.5)
Top Groups
1 Performers  (9.3)
2 Booze Design  (9.3)
3 Oxyron  (9.3)
4 Nostalgia  (9.3)
5 Censor Design  (9.3)
Top Graphicians
1 Mirage  (9.7)
2 Archmage  (9.7)
3 Mikael  (9.6)
4 Carrion  (9.6)
5 Sulevi  (9.6)

Home - Disclaimer
Copyright © No Name 2001-2024
Page generated in: 0.062 sec.