There are ways to convert it, I am shure, but I haven't one "quick and shure" by the hand. For MacOS 9 we had a "ResEdit", which was able to change the type of a file and/or the creator. Same did FileTyper. Try to use another editor. Maybe he's not so gingerly. Open and save it under a new name. Maybe this changes to a creator, BBedit accepts. Or try a Hexeditor. Some free ones do "compare" too and have a Text-preview.
I like TRIGON too. It's interesting to work with the primitive body generation by VERT and PGON. Slowly I come behind some secrets. Is a lot of math, but fun.
I improved the object a bit to be freely rotateable in space. So you can place a couple of triangles on the floor plan drag all points at their positions, aktivate all and, if shurely all have the same basepoint, you can rotate the whole shape freely in space. Or save it as a new 3D-Object. Model in floor plan and rotate to the facade. Next step will be numbering the borders, drawing a true flat shape in floor plan to make a material list (or a folding plan to cut and make a real model) and realize exact texture wrapping. I am not shure, if I will make it public domain or try to get some money for it (depends of the time investment).
I like TRIGON too. It's interesting to work with the primitive body generation by VERT and PGON. Slowly I come behind some secrets. Is a lot of math, but fun.
I improved the object a bit to be freely rotateable in space. So you can place a couple of triangles on the floor plan drag all points at their positions, aktivate all and, if shurely all have the same basepoint, you can rotate the whole shape freely in space. Or save it as a new 3D-Object. Model in floor plan and rotate to the facade. Next step will be numbering the borders, drawing a true flat shape in floor plan to make a material list (or a folding plan to cut and make a real model) and realize exact texture wrapping. I am not shure, if I will make it public domain or try to get some money for it (depends of the time investment).
- I can control each vertex by a graphical hotspot to move
- I can switch (un)visible each edge
- I can wrap on it a texture exactly (see a thread half a year ago)
- In this case: I could export the nodes, edges, pgon etc. to file and could autoscript a native GDL by graphical changes.
- I can do some math again.
I started working with it by writing an polygonal object, which spans a web of triangles. Each node I can lift and move as the freeform tool. This web I can give any surface none of the predefined commands can give to me. All I need is the algorithm to calculate the vertices. And that all by the full control of each triangle in space. First I did a flag, which flutters in the wind nearly realistic, because each triangle depends of its neighboured one. A bit like infinte element calculation. And the algorithm has some random components to make it not look like a sinus-wave. One problem was, and this caused the thread about the TEVE-command, that no GDL command wraps a texture or picture exactly on a folded surface. If you get high hills and deep valleys each command looses the exact connection to the next triangles. Only TEVE does this job. And this causes working with primitives.
I am still looking for a easy to GDL transferable algorithm to calculate nurbs or blobs. I am happy to have found one for splines. I first step, but still on the hunt. But before I have find some ... time.😉
- I can switch (un)visible each edge
- I can wrap on it a texture exactly (see a thread half a year ago)
- In this case: I could export the nodes, edges, pgon etc. to file and could autoscript a native GDL by graphical changes.
- I can do some math again.
I started working with it by writing an polygonal object, which spans a web of triangles. Each node I can lift and move as the freeform tool. This web I can give any surface none of the predefined commands can give to me. All I need is the algorithm to calculate the vertices. And that all by the full control of each triangle in space. First I did a flag, which flutters in the wind nearly realistic, because each triangle depends of its neighboured one. A bit like infinte element calculation. And the algorithm has some random components to make it not look like a sinus-wave. One problem was, and this caused the thread about the TEVE-command, that no GDL command wraps a texture or picture exactly on a folded surface. If you get high hills and deep valleys each command looses the exact connection to the next triangles. Only TEVE does this job. And this causes working with primitives.
I am still looking for a easy to GDL transferable algorithm to calculate nurbs or blobs. I am happy to have found one for splines. I first step, but still on the hunt. But before I have find some ... time.
I have heard of "finite element calculation"A misspelling late at night.
but not infinte element calculation.
What is that ?
The elements are "finite", otherwise my object wouldn't end.
But now you have an overview of the editor market. You haven't found an editor, which compares two ".gsm" files without changing their creator, isn't it? Would have been funny too.
