Browsing this Thread:
1 Anonymous Users
|
Re: Slightly OT: Problem with GCC under Linux (Ubuntu 64Bit)
|
||||
|---|---|---|---|---|
|
Home away from home
![]() |
I got over my problem with image converters.
The Image Magick bundle came with some cli commands that could edit, change or convert graphic. A simple command line like:
convert mapfull.png -depth 8 mapfull.rgb
Was all I need, the Image Magick Picture viewer has some interesting convert functions but *.rgb may have been a SGI format with run length compressions. The convert command was able to do the conversion of the 32768x32768 image format ... but it needed some minutes for this huge file. --- Maybe someone is asking what Map I wanted to convert, this was a Map from the Amiga game 'The Faery Tale Adventure' I just want to know how to handle such gigantic 2D Maps on a game. I want to play around with its fine graphic maybe I will try and make some tribute RPG that acts as some kind of demo for this game.
Posted on: 2016/8/15 22:20
|
|||
|
||||
|
Re: Slightly OT: Problem with GCC under Linux (Ubuntu 64Bit)
|
||||
|---|---|---|---|---|
|
Home away from home
![]() |
Thanks for your help, your answer made me look for the filesize.
--- I had a update, but it was worthless. Explanation: I have a MAP of the RPG/Adventure saved as PNG, I could open the PNG under Windows with Irfan View, but the file is extreme big. The image size is 32768x32768 Pixels this means it needs 4GB when loaded as RBGA. The file I was working on, had only a quarter of this size (16384x16384) was exported as RAW (RBG/RGBA ?) via Irfan view. The file size was exactly 1GB (like I expected for RGBA) but it only consisted of values between 00 and 05 so it seems be faulty. When using Image Magick (under Linux) my little system is crashing when I try to view the 1GPixel file, when exporting the smaller files as RGB, they only have a size of ~8MB, much less of the size I expected. I never tried opening the Images under SDL, because I thought my tools for image export where OK, but they are not.
Posted on: 2016/8/15 9:10
|
|||
|
||||
|
Re: Slightly OT: Problem with GCC under Linux (Ubuntu 64Bit)
|
||||
|---|---|---|---|---|
|
Home away from home
![]()
|
Yes, that's probably what happened. I hope you have a backup
Good luck with the rest of the program.
Posted on: 2016/8/14 15:29
|
|||
|
||||
|
Re: Slightly OT: Problem with GCC under Linux (Ubuntu 64Bit)
|
||||
|---|---|---|---|---|
|
Home away from home
![]() |
Ooops sorry maybe it was a false alarm.
I chhecked the file with ls -la again, filesize is 0 ... maybe because I opened it accidently with 'w' first ...
Posted on: 2016/8/12 22:49
|
|||
|
||||
|
Re: Slightly OT: Problem with GCC under Linux (Ubuntu 64Bit)
|
||||
|---|---|---|---|---|
|
Home away from home
![]()
|
That's weird. It works for me on 64-bit Darwin with a 1.6GB file. Have you tried with other large files?
Posted on: 2016/8/12 20:52
|
|||
|
||||
|
Slightly OT: Problem with GCC under Linux (Ubuntu 64Bit)
|
||||
|---|---|---|---|---|
|
Home away from home
![]() |
I know this is not a Linux forum, but I have a problem with fread() on Linux AMD64 (Ubuntu).
If I am usingf fread() on a small file, it works like it should be. But currently I want to do some conversions on the Map of on old Amiga adventure. This Map has a size of around 1GB of Data, I know it will be to big for the computers memory, therefore I'm reading small Blocks of Data with fread() but it doesn't work like it should be. I know there can be some problems using fseek() on files > 4GB or there could be a problem with the filesystem but I don't understand the problems when using plain fread(). Code:
// compile with gcc myprog myprog.c
When reading from a small file, it works without problems, when reading from a file with 1GB Filesize it doesn't read a single block of Data results small file:
./fread fread.cPROCESSING: Block 0
results big file:
./fread mapfull_RGB.raw
Posted on: 2016/8/12 15:26
|
|||
|
||||
You can view topic.
You cannot start a new topic.
You cannot reply to posts.
You cannot edit your posts.
You cannot delete your posts.
You cannot add new polls.
You cannot vote in polls.
You cannot attach files to posts.
You cannot post without approval.
You cannot use topic type.
You cannot use HTML syntax.
You cannot use signature.
You cannot create PDF files.
You cannot get print page.






Good luck with the rest of the program.