Sign in to follow this  
codename47

OpenGL .max format question

Recommended Posts

Hi All; I have 2 question about "*.max" format Q1) Is it possible to open "*.max" files with a program other then "3ds max"?(blender .. etc) I know deep exploration can open, but it uses "3ds max" to pen, so it is not a solution for me :( Q2) Is it possible to load "*.max" files to an OpenGL based 3D application without any conversion. Actually we have a game-like system and we want to use existing *.max extensioned files in our system. Conversion (converting "*.max" files to more common format) is not solution for my case. Well, it can be a solution but if we can open it with a program other than "3ds max" As you all understand, price of "3ds max" will increase the project cost. Because we have to buy lots of licenses. May be open source tools can handle this problem.(if its possible of course) I just wanted to ask whether you have an idea. Have a nice day..

Share this post


Link to post
Share on other sites
Hello!

I have done a lot of things with several 3D formats and I can tell you with friendly aspects: forget it. The only thing you could do is to use 3DSMAX DCOM interface (I believe it's called like that) which makes it possible to load .max files but you have to have 3DS MAX installed.

So if you plan an application/game which uses .max directly, you will have to shipp 3dsmax as well, which makes no sense.

The Deep Exploration application uses this interface which makes it possible to access .max files.

What you have to do is to take some exporter plugins and export data from max or use the Export to .ASE feature, which is also detailed a lot.

Share this post


Link to post
Share on other sites
Q1)
blender doesn't seem to support .max but it does support .3ds, .max isnt a very good format since it saves a lot of junk thats serves no purpose outside 3dsmax, you probably want a mesh file

Q2)
gl doesn't load any files natively but you can probably find some free libs to do the trick

Share this post


Link to post
Share on other sites
Quote:
Original post by codename47
As you all understand, price of "3ds max" will increase the project cost. Because we have to buy lots of licenses. May be open source tools can handle this problem.(if its possible of course) I just wanted to ask whether you have an idea.


You're basically saying you don't want to buy max licenses? There are a few free packages out there you can use instead - blender for example. Xsi is another choice, which is much cheaper than max (and better). None of them will open *.max files though. Normally you'd just export from max/xsi whatever into some file format to grab the data from (eg, collada, fbx, dotxsi, etc). It's then a case of dumping that data into a custom format for your game (and writing the loader since openGL doesn't understand any data formats). You can use libs such as cal3d to do the engine part if needed....

Share this post


Link to post
Share on other sites
Hi Again;

Thank you so much for the answers. Seems like there is no solution other than buying "3ds max" :( BTW I saw a program called "Alteros 3D" (http://www.lighttek.com/alteros/index.htm) it can open .max files but without textures and most of the time with wrong geometry. Actually they say, "we are providing limited support for .max files" So after some try, I realized that this program is not exact solution for my problem. But thing that confuses my mind is, how this program manages to open.max files.

I think same problem exist in importing .max file directly to a real-time OpenGL application. Seems like it is almost impossible to find a loader for .max

Share this post


Link to post
Share on other sites
Quote:
Original post by codename47
Seems like it is almost impossible to find a loader for .max


It is impossible to find a loader for .max files. The same is true of Maya and Xsi files. The *.max files will contain

- the INodes that exist. For example, a poly cube node with attributes "width", "height", "divisions height" etc. It will not store points and normals for things it is automatically generating.

- the layout of the windows when the file was saved.

- the selected items when saved etc.

- and a whole host of other crap that you either, cannot replicate without writing the entirity of Max, or is simply not relevent to even bother.

Max files have to be opened by Max. period. However, no one uses max files for games, so it's fine. Instead they *always* export to a file format that contains the useful information that they want (i.e. verts/normals/animation data etc). So, it does not matter what package you use to author your data, you *will* have to find a way to export that data into something useful. (use fbx for example to export data from Max and load into Xsi or Maya). Common file formats that exist that already do this (and have plug-ins for max/maya/xsi etc) are fbx, collada and dotxsi. Use one of those to load the data into a real time app....

Share this post


Link to post
Share on other sites
hey

Ya know I think there is a trail version of 3dsmax (well there used to be), if you have files you must convert then maybe use the trial version todo this, and then start making ya models with something else. I recommend blender, it's opensource and free, and most importantly it's a great package.

Hmm, otherwise maybe you can open .max files with gmax, I think gmax is a free version of 3dsmax or something, dunno exactly.

edit
Yep, just took a little visit to the discreet/autodesk website, and I think you can download the trial version here.

another edit
I just done a lil googling, and found that gmax no longer exists or something, and I also found that it couldn't open/import .max files anyhows.

Anyhows if you have already used up the trial or something, then maybe you could ask someone with 3dsmax to convert the files for ya? I assume you have files to convert anyhows, hehe. Maybe ask at #3dsmax EFNet (irc), or on a forum somewhere.

cyas

[Edited by - yosh64 on January 28, 2008 4:09:39 PM]

Share this post


Link to post
Share on other sites
Yes,

1- Get the trial as yosh64 pointed out but do not install it just yet
2- Get Collada Max (http://www.feelingsoftware.com)
3- Get the FBX Plugin (http://usa.autodesk.com/adsk/servlet/index?siteID=123112&id=6839916)
4- Get CrossWalk (http://www.softimage.com/downloads/Crosswalk)
5- Get Any other plugin for a format you want to export to that isn't included in Max
6- Gather the collection of .max files you want to use in your game
7- Install Max Trial
8- Install all the plugins you gathered
9- Arm yourself with patience and export each of the files you want into as many formats as you may need.

Once you have your new collection of assorted formats, find a DCC package you can afford, import the exported files and work on them there.

The COLLADA format will probably give you the best translation/interpretation of data (minimal loss of features), whereas with .3ds and .obj you will lose skinning and probably animation.

Cheers!

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this  

  • Announcements

  • Forum Statistics

    • Total Topics
      628300
    • Total Posts
      2981900
  • Similar Content

    • By mellinoe
      Hi all,
      First time poster here, although I've been reading posts here for quite a while. This place has been invaluable for learning graphics programming -- thanks for a great resource!
      Right now, I'm working on a graphics abstraction layer for .NET which supports D3D11, Vulkan, and OpenGL at the moment. I have implemented most of my planned features already, and things are working well. Some remaining features that I am planning are Compute Shaders, and some flavor of read-write shader resources. At the moment, my shaders can just get simple read-only access to a uniform (or constant) buffer, a texture, or a sampler. Unfortunately, I'm having a tough time grasping the distinctions between all of the different kinds of read-write resources that are available. In D3D alone, there seem to be 5 or 6 different kinds of resources with similar but different characteristics. On top of that, I get the impression that some of them are more or less "obsoleted" by the newer kinds, and don't have much of a place in modern code. There seem to be a few pivots:
      The data source/destination (buffer or texture) Read-write or read-only Structured or unstructured (?) Ordered vs unordered (?) These are just my observations based on a lot of MSDN and OpenGL doc reading. For my library, I'm not interested in exposing every possibility to the user -- just trying to find a good "middle-ground" that can be represented cleanly across API's which is good enough for common scenarios.
      Can anyone give a sort of "overview" of the different options, and perhaps compare/contrast the concepts between Direct3D, OpenGL, and Vulkan? I'd also be very interested in hearing how other folks have abstracted these concepts in their libraries.
    • By aejt
      I recently started getting into graphics programming (2nd try, first try was many years ago) and I'm working on a 3d rendering engine which I hope to be able to make a 3D game with sooner or later. I have plenty of C++ experience, but not a lot when it comes to graphics, and while it's definitely going much better this time, I'm having trouble figuring out how assets are usually handled by engines.
      I'm not having trouble with handling the GPU resources, but more so with how the resources should be defined and used in the system (materials, models, etc).
      This is my plan now, I've implemented most of it except for the XML parts and factories and those are the ones I'm not sure of at all:
      I have these classes:
      For GPU resources:
      Geometry: holds and manages everything needed to render a geometry: VAO, VBO, EBO. Texture: holds and manages a texture which is loaded into the GPU. Shader: holds and manages a shader which is loaded into the GPU. For assets relying on GPU resources:
      Material: holds a shader resource, multiple texture resources, as well as uniform settings. Mesh: holds a geometry and a material. Model: holds multiple meshes, possibly in a tree structure to more easily support skinning later on? For handling GPU resources:
      ResourceCache<T>: T can be any resource loaded into the GPU. It owns these resources and only hands out handles to them on request (currently string identifiers are used when requesting handles, but all resources are stored in a vector and each handle only contains resource's index in that vector) Resource<T>: The handles given out from ResourceCache. The handles are reference counted and to get the underlying resource you simply deference like with pointers (*handle).  
      And my plan is to define everything into these XML documents to abstract away files:
      Resources.xml for ref-counted GPU resources (geometry, shaders, textures) Resources are assigned names/ids and resource files, and possibly some attributes (what vertex attributes does this geometry have? what vertex attributes does this shader expect? what uniforms does this shader use? and so on) Are reference counted using ResourceCache<T> Assets.xml for assets using the GPU resources (materials, meshes, models) Assets are not reference counted, but they hold handles to ref-counted resources. References the resources defined in Resources.xml by names/ids. The XMLs are loaded into some structure in memory which is then used for loading the resources/assets using factory classes:
      Factory classes for resources:
      For example, a texture factory could contain the texture definitions from the XML containing data about textures in the game, as well as a cache containing all loaded textures. This means it has mappings from each name/id to a file and when asked to load a texture with a name/id, it can look up its path and use a "BinaryLoader" to either load the file and create the resource directly, or asynchronously load the file's data into a queue which then can be read from later to create the resources synchronously in the GL context. These factories only return handles.
      Factory classes for assets:
      Much like for resources, these classes contain the definitions for the assets they can load. For example, with the definition the MaterialFactory will know which shader, textures and possibly uniform a certain material has, and with the help of TextureFactory and ShaderFactory, it can retrieve handles to the resources it needs (Shader + Textures), setup itself from XML data (uniform values), and return a created instance of requested material. These factories return actual instances, not handles (but the instances contain handles).
       
       
      Is this a good or commonly used approach? Is this going to bite me in the ass later on? Are there other more preferable approaches? Is this outside of the scope of a 3d renderer and should be on the engine side? I'd love to receive and kind of advice or suggestions!
      Thanks!
    • By nedondev
      I 'm learning how to create game by using opengl with c/c++ coding, so here is my fist game. In video description also have game contain in Dropbox. May be I will make it better in future.
      Thanks.
    • By Abecederia
      So I've recently started learning some GLSL and now I'm toying with a POM shader. I'm trying to optimize it and notice that it starts having issues at high texture sizes, especially with self-shadowing.
      Now I know POM is expensive either way, but would pulling the heightmap out of the normalmap alpha channel and in it's own 8bit texture make doing all those dozens of texture fetches more cheap? Or is everything in the cache aligned to 32bit anyway? I haven't implemented texture compression yet, I think that would help? But regardless, should there be a performance boost from decoupling the heightmap? I could also keep it in a lower resolution than the normalmap if that would improve performance.
      Any help is much appreciated, please keep in mind I'm somewhat of a newbie. Thanks!
    • By test opty
      Hi,
      I'm trying to learn OpenGL through a website and have proceeded until this page of it. The output is a simple triangle. The problem is the complexity.
      I have read that page several times and tried to analyse the code but I haven't understood the code properly and completely yet. This is the code:
       
      #include <glad/glad.h> #include <GLFW/glfw3.h> #include <C:\Users\Abbasi\Desktop\std_lib_facilities_4.h> using namespace std; //****************************************************************************** void framebuffer_size_callback(GLFWwindow* window, int width, int height); void processInput(GLFWwindow *window); // settings const unsigned int SCR_WIDTH = 800; const unsigned int SCR_HEIGHT = 600; const char *vertexShaderSource = "#version 330 core\n" "layout (location = 0) in vec3 aPos;\n" "void main()\n" "{\n" " gl_Position = vec4(aPos.x, aPos.y, aPos.z, 1.0);\n" "}\0"; const char *fragmentShaderSource = "#version 330 core\n" "out vec4 FragColor;\n" "void main()\n" "{\n" " FragColor = vec4(1.0f, 0.5f, 0.2f, 1.0f);\n" "}\n\0"; //******************************* int main() { // glfw: initialize and configure // ------------------------------ glfwInit(); glfwWindowHint(GLFW_CONTEXT_VERSION_MAJOR, 3); glfwWindowHint(GLFW_CONTEXT_VERSION_MINOR, 3); glfwWindowHint(GLFW_OPENGL_PROFILE, GLFW_OPENGL_CORE_PROFILE); // glfw window creation GLFWwindow* window = glfwCreateWindow(SCR_WIDTH, SCR_HEIGHT, "My First Triangle", nullptr, nullptr); if (window == nullptr) { cout << "Failed to create GLFW window" << endl; glfwTerminate(); return -1; } glfwMakeContextCurrent(window); glfwSetFramebufferSizeCallback(window, framebuffer_size_callback); // glad: load all OpenGL function pointers if (!gladLoadGLLoader((GLADloadproc)glfwGetProcAddress)) { cout << "Failed to initialize GLAD" << endl; return -1; } // build and compile our shader program // vertex shader int vertexShader = glCreateShader(GL_VERTEX_SHADER); glShaderSource(vertexShader, 1, &vertexShaderSource, nullptr); glCompileShader(vertexShader); // check for shader compile errors int success; char infoLog[512]; glGetShaderiv(vertexShader, GL_COMPILE_STATUS, &success); if (!success) { glGetShaderInfoLog(vertexShader, 512, nullptr, infoLog); cout << "ERROR::SHADER::VERTEX::COMPILATION_FAILED\n" << infoLog << endl; } // fragment shader int fragmentShader = glCreateShader(GL_FRAGMENT_SHADER); glShaderSource(fragmentShader, 1, &fragmentShaderSource, nullptr); glCompileShader(fragmentShader); // check for shader compile errors glGetShaderiv(fragmentShader, GL_COMPILE_STATUS, &success); if (!success) { glGetShaderInfoLog(fragmentShader, 512, nullptr, infoLog); cout << "ERROR::SHADER::FRAGMENT::COMPILATION_FAILED\n" << infoLog << endl; } // link shaders int shaderProgram = glCreateProgram(); glAttachShader(shaderProgram, vertexShader); glAttachShader(shaderProgram, fragmentShader); glLinkProgram(shaderProgram); // check for linking errors glGetProgramiv(shaderProgram, GL_LINK_STATUS, &success); if (!success) { glGetProgramInfoLog(shaderProgram, 512, nullptr, infoLog); cout << "ERROR::SHADER::PROGRAM::LINKING_FAILED\n" << infoLog << endl; } glDeleteShader(vertexShader); glDeleteShader(fragmentShader); // set up vertex data (and buffer(s)) and configure vertex attributes float vertices[] = { -0.5f, -0.5f, 0.0f, // left 0.5f, -0.5f, 0.0f, // right 0.0f, 0.5f, 0.0f // top }; unsigned int VBO, VAO; glGenVertexArrays(1, &VAO); glGenBuffers(1, &VBO); // bind the Vertex Array Object first, then bind and set vertex buffer(s), //and then configure vertex attributes(s). glBindVertexArray(VAO); glBindBuffer(GL_ARRAY_BUFFER, VBO); glBufferData(GL_ARRAY_BUFFER, sizeof(vertices), vertices, GL_STATIC_DRAW); glVertexAttribPointer(0, 3, GL_FLOAT, GL_FALSE, 3 * sizeof(float), (void*)0); glEnableVertexAttribArray(0); // note that this is allowed, the call to glVertexAttribPointer registered VBO // as the vertex attribute's bound vertex buffer object so afterwards we can safely unbind glBindBuffer(GL_ARRAY_BUFFER, 0); // You can unbind the VAO afterwards so other VAO calls won't accidentally // modify this VAO, but this rarely happens. Modifying other // VAOs requires a call to glBindVertexArray anyways so we generally don't unbind // VAOs (nor VBOs) when it's not directly necessary. glBindVertexArray(0); // uncomment this call to draw in wireframe polygons. //glPolygonMode(GL_FRONT_AND_BACK, GL_LINE); // render loop while (!glfwWindowShouldClose(window)) { // input // ----- processInput(window); // render // ------ glClearColor(0.2f, 0.3f, 0.3f, 1.0f); glClear(GL_COLOR_BUFFER_BIT); // draw our first triangle glUseProgram(shaderProgram); glBindVertexArray(VAO); // seeing as we only have a single VAO there's no need to // bind it every time, but we'll do so to keep things a bit more organized glDrawArrays(GL_TRIANGLES, 0, 3); // glBindVertexArray(0); // no need to unbind it every time // glfw: swap buffers and poll IO events (keys pressed/released, mouse moved etc.) glfwSwapBuffers(window); glfwPollEvents(); } // optional: de-allocate all resources once they've outlived their purpose: glDeleteVertexArrays(1, &VAO); glDeleteBuffers(1, &VBO); // glfw: terminate, clearing all previously allocated GLFW resources. glfwTerminate(); return 0; } //************************************************** // process all input: query GLFW whether relevant keys are pressed/released // this frame and react accordingly void processInput(GLFWwindow *window) { if (glfwGetKey(window, GLFW_KEY_ESCAPE) == GLFW_PRESS) glfwSetWindowShouldClose(window, true); } //******************************************************************** // glfw: whenever the window size changed (by OS or user resize) this callback function executes void framebuffer_size_callback(GLFWwindow* window, int width, int height) { // make sure the viewport matches the new window dimensions; note that width and // height will be significantly larger than specified on retina displays. glViewport(0, 0, width, height); } As you see, about 200 lines of complicated code only for a simple triangle. 
      I don't know what parts are necessary for that output. And also, what the correct order of instructions for such an output or programs is, generally. That start point is too complex for a beginner of OpenGL like me and I don't know how to make the issue solved. What are your ideas please? What is the way to figure both the code and the whole program out correctly please?
      I wish I'd read a reference that would teach me OpenGL through a step-by-step method. 
  • Popular Now