3D Modeler for Icaros

miker1264 · 16820

« previous next »
Pages: 1 2 3 4 ... 8   Go Down

dizzy

  • Junior Member
  • **
    • Posts: 59
    • Karma: +60/-0
    • YouTube channel
Reply #15 on: June 21, 2019, 04:17:11 PM
Quote from: paolone on June 21, 2019, 04:11:58 PM
I like the idea of a 3D modeler. Although the best option would be porting Blender to AROS (there is a OS4 version... so it shouldn't impossible to port), I can perfectly understand it would be a huge task to perform.
So please port what's more comfortable to you: having a simple modeler is far better than having NO modeler. :-)
Thumbs up and good luck! For the STLView code you can use it at will (public domain now after) an make it actually do something useful. Do with it what you want. Thank Deadwood for the inner workings... :)
« Last Edit: June 21, 2019, 04:28:43 PM by dizzy »


salvatore

  • Guest
Reply #16 on: June 21, 2019, 04:33:38 PM
guys it's gonna be a great job, believe me ;)


miker1264

  • Legendary Member
  • *****
    • Posts: 1563
    • Karma: +83/-6
Reply #17 on: June 21, 2019, 04:39:38 PM
paolone,

I agree that a more modern 3D modeler like Blender which I believe originated on the Amiga as "Traces/Blender" would be optimal. But we have to start somewhere. Once RayStorm is working on AROS the sources will be available so that we will have a good understanding of what is involved.


salvatore

  • Guest
Reply #18 on: June 21, 2019, 04:50:27 PM
yes I know that only currently has abandoned the old rendering engine, this means that raystorm is not antiquity


salvatore

  • Guest
Reply #19 on: June 21, 2019, 04:53:29 PM
it seems to me that cmq must first bring phyton to a certain version that I do not remember and then put hand to the code of blender, so I make you think about the work that there would be to do


dizzy

  • Junior Member
  • **
    • Posts: 59
    • Karma: +60/-0
    • YouTube channel
Reply #20 on: June 21, 2019, 06:08:26 PM
There was a limit on the size of the VBO buffer, but not on the number of buffers if I recall it correctly. If one object exceeds the buffer then another buffer needs to be allocated for the object... There might be some bugs on the STLView code such that the VBO is loaded everytime the scene is updated, but it isn't relly needed... :) Also the code doesn't check if the vertices/STL file is/are valid. See else where the STL definition...

It doesn't take much to show one single 3D rendering on AROS, but for multiple of objects some sort of allocator is needed for the objects in VBO. When the renderer is coded in object oriented way then it just starts to work. Render this and render that... Like magic...
« Last Edit: June 21, 2019, 06:23:04 PM by dizzy »


salvatore

  • Guest
Reply #21 on: June 21, 2019, 06:14:28 PM
as I understand it miker has a certain dime on these programs, there will be no problems dizzy

hi


dizzy

  • Junior Member
  • **
    • Posts: 59
    • Karma: +60/-0
    • YouTube channel
Reply #22 on: June 21, 2019, 06:25:19 PM
Quote from: salvatore on June 21, 2019, 06:14:28 PM
as I understand it miker has a certain dime on these programs, there will be no problems dizzy

hi
Great! But if there is anything he needs I hope we can help him forwards.


salvatore

  • Guest
Reply #23 on: June 21, 2019, 06:30:32 PM
So far, everything's fine


terminills

  • Member
  • ***
    • Posts: 140
    • Karma: +65/-0
Reply #24 on: June 21, 2019, 09:14:05 PM


miker1264

  • Legendary Member
  • *****
    • Posts: 1563
    • Karma: +83/-6
Reply #25 on: June 21, 2019, 09:15:45 PM
Having a good understanding of Open GL and the rendering process is important but my main goal is to revise and compile the source code to work on AROS at the moment. If AROS meets the requirements such that StormMesa and the AROS implementation are compatible when compiled for AROS it should work. At that point if it doesn't then I'll look further to find out what's needed. 

But for the moment all is going well.


miker1264

  • Legendary Member
  • *****
    • Posts: 1563
    • Karma: +83/-6
Reply #26 on: June 21, 2019, 10:06:56 PM
terminills,

Thank you. I'll update my sources to reflect the recent changes to kalamatee's repository.


salvatore

  • Guest
Reply #27 on: June 21, 2019, 10:20:11 PM
I'm glad the work is going well ;)


salvatore

  • Guest
Reply #28 on: June 21, 2019, 10:59:52 PM
I'm sorry I didn't know about the kalamatee github


miker1264

  • Legendary Member
  • *****
    • Posts: 1563
    • Karma: +83/-6
Reply #29 on: June 24, 2019, 07:22:06 AM
Here is the new Image Viewer, a sample image, the source code
and some new icons for the Modeler Component and the Viewer.

The Original RayStorm Image Viewer was outdated & was based
on older techniques intended for a Non-Amiga-Like operating
system using some so-called "Libraries" to read picture files.

That process seemed to not take advantage of the power of the
Picture DataTypes while utilizing them only as a “last resort”.
The New Image Viewer would use Picture DataTypes for
all it functions making it more flexible & also more efficient.

It now supports whichever Picture Types that the AROS Picture
DataTypes can read, meaning all ILBM file types as well as HAM6,
and HAM8 images, & also GIF, BMP, JPG, PNM, PNG, PCX & TGA.
Additionally, it now displays images with 32 bit RGB + Alpha.

Whenever a new Picture DataType is available for AROS, including
the newest SVG, or a future TIFF, or anything else, the New Image
Viewer will be capable of using the DataTypes to display those
Picture Types without any revisions to the current source code.

In short, the New Image Viewer is more efficient, more inclusive
& more extensible. Like the "Viewer" it's a standalone component.
There are probably some areas where it can be optimized. I put it
together in about four hours this weekend. The icon took another
hour to put together. Next I'll move on to the Modeler Component.

Try out the image viewer & let me how it works for you. I've tested
the New Image Viewer on Icaros Hosted on Windows & Icaros Native.



Pages: 1 2 3 4 ... 8   Go Up
« previous next »