return to q&a page

Interview first posted
5 March 2002
and
2 APril 2002

return to upFront.eZIne

 

q & a

five minutes with 
Okino Computer
Graphics


Okino Computer Graphics
3397 American Drive
Unit # 1
Mississauga, Ontario
L4V 1T8, Canada

 

Sales
sales@okino.com

 

www.okino.com

 

Phone: (905) 672-9328

(888) 3D-OKINO (Toll Free)

Fax: (905) 672-2706

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

  

 

  


Robert Lansdale heads up Okino Computer Graphics, a company that specializes in translation in both the CAD and rendering worlds.

- - -

upFront.eZine: How did you get started in what you do?

Mr. Lansdale: 1988 was the time of Alias 1.0, CAD-3D on the Atari, Caligari, and the forerunners of today's major animation packages. Because I couldn't afford Alias or RenderMan, I decided to drop everything and write NuGraf as a clone of the best of what was the market at that time.
        From day 1, my mind had been set on creating one of the best all-around toolkits available, encompassing geometry pipelines, color conversion, MIPMAP/EWA filtering (my master's thesis), low memory usage, scanline rendering, and so on. Three years later, it was ready:  a "3D Studio r1.0" product, without the user interface, for developers to directly drop into their product. By 1997, we began to hook up our toolkit within package, such as 3DS MAX and Maya, as native plug-ins.
        One of the most popular conversion routes at that time, and still to this day, is the Lightwave <-> 3D Studio conversion. I spent about four years developing the underlying conversion pipeline and cloning the file format and functionality of these respective programs.

 

upFront.eZine: So that's the rendering market. What's the CAD connection for you?

Mr. Lansdale: In short, NuGraf is marketed to CAD world, and PolyTrans to rest of 3D world. They are identical packages at the core level.
        The tie-in for the CAD market is that in 1989 I discovered that my 'reason to be on earth' was to write data translation systems. That year I began a well-received IGES import converter. This lead to our Wavefront .obj importer system in 1992, .3ds importer in 1993, Lightwave 'clone'  importer in 1994, and DXF in 1995. The number of converters never let up!
       In the early days, each of these converters was a means to import complete 3D datatsets for rendering into our NuGraf toolkit software, because our company policy is "no modeling." We wrote our converters to bring in all scene content, including materials and texture mapping. Thus, we had a powerful 3D rendering/database toolkit underlying these geometry converters.
        NuGraf proper found its niche a low-cost high-speed solution for the import, optimization, and rendering of Pro/Engineer data. That's why our Web site has a large number of Pro/E images. The IGES converter, which I had started in 1989, was the savior to the import of Pro/E data to NuGraf.

 

upFront.eZine: How does your PolyTrans product fit into all this?

Mr. Lansdale: Back in the summer 1996, people at Siggraph wanted us to make a data translation product, so I renamed NuGraf to the PolyTrans name, stripped out rendering, material editing, texture editing, complex UI, simplified the manuals, and a new product was born. By October 1996 sales zipped up and within a year we had sold to almost every game developer (although game developers are now a tiny portion of our user base).
        We were the first license of Geomware's NLIB (now SMLIB) library, and introduced complete import, cleansing, and conversion of 144/142 trimmed NURBS IGES files. In the same timeframe came the licensing of ACIS as a conversion pipeline (I believe we were the first); the development of our OLE D&M interface for SolidWorks and Solid Edge -- I don't think too many others ever implement OLE D&M [Microsoft's ill-fated object linking and embedding for design and modeling] -- XGL, VET, and so on.

 

upFront.eZine: Tell me a little bit more about your company.

Mr. Lansdale: I am not "Mr Okino" and I don't sit in a small room answering phone calls, eating beer and pizza, responding to email and shipping products (although some customers initially assume so). We're a private Canadian corporation, located in Toronto with 11 to 12 employees. Okino was named after Professor Okino in a book by Nadia Magnenat-Thalmann and Daniel Thalmann. We are not a Japanese company.
        Our primary goals are to create a great general purpose tool that will satisfy the needs of all 3D people, when they have a problem to solve. Tools that don't die when presented with overly large datasets. To provide a neutral, politics-free, "universal" conversion hub of translation software. To provide a technical means to connect the CAD, VisSim and 3D multimedia worlds as no one else has tried in one package. To provide tech support that is knowledgeable, friendly, and from the mouths of the programmers themselves.

Back in 1992, the president of NeoVisuals told me, "Solve people's problems and they will beat a path to your door." What we offer are solutions to major problems encountered by our users. Most of the emails I get each day usually start with, "I have a problem. Can you help?" Our converters are the hammer and nails; my hands-on tech support tells people how to solve their problems.
        As much as 3D animation packages are expensive and great for modeling/rendering/animation, they were never designed to handle large data translation projects. Since I had optimized our core toolkit for 286-based PC/IRIX machines, it was always fast and memory efficient. When doing 200MB IGES files, or 300MB SoftImage-to-Maya conversions, this makes all the difference in the world.

One of many hidden uses of our software is as a stepping stone. Complex CAD files are imported into NuGraf/PolyTrans, simplified in part count, and then fed to other formats in a clean state. This is particularly important for moving CAD data to MAX, Maya and Lightwave these days. Few people consider this when purchasing our software, but come to realize its power in production conditions.

        Look at all major 3D animation/modeling/CAD packages, take off the top 10%, and ask: "How serious are they about data translation?" Most are not. This hasn't changed much in over 10 years. That's where my outright love of supporting data translation software development has helped the 3D community. Our focus has been to "be a universal hub for data translation in a 3D world where companies do not wish to exchange their data with competing packages. We want to create an open market for data translation, instead of using politics and other tactics to prevent data translation.

        Such politics occur as "data inter-operability" that is usually only to the advantage to a company when data can be imported into their proprietary package, and not exported. Data translation was not been taken seriously for a large part of the 1990s. I have lobbied to make people aware that conversion software actually "does work" (the kinks in the pipeline are usually the source/destination programs).

And this is a statement I keep hammering to people indirectly: the converters we write take months or years to write, even though some people mention that their cousin or son in high school can do it in an afternoon.

        Creating a converter is like raising a child (see my comments at http://www.okino.com/conv/filefrmt.htm . Writing a converter is not about importing a mesh dataset from a file, but rather dealing with all the got-chas that befall end-users.

 

And my final point is the one that is the hardest to overcome on a daily basis. I purchase software for my company. When I purchase a package, I rarely consider what the company must be like, who writes the software, or what support they can provide.

        In my dream world, however, every 3D package would come with a history and hands-on account about how the software was developed. I know some history of programs -- like 3DStudio, Lightwave, Caligari, Maya/Alias, and SoftImage -- were developed, and I feel much closer to those packages and can respect the effort that went into them. I respect how some of these developers toiled untold hours over their software.

        New users to our product come to us as if support is supposed to provide a robotic answer, but they find over time that there are real people here who want to help directly. Support to me is not about answering questions, but about staying awake until the head hits the keyboard solving a problem because the customer has a production deadline the next morning.

        This form of support has lead to many great email and customer friendships over the years. My point is that our Web site shows NuGraf and PolyTrans with a well- established user list, good set of features, and a stable company. But there is little sense of the back-end humanity that comes with the purchase price.

 

 Return to www.upfrontezine.com.

 

Entire contents copyright ©2002 by upFront.eZine Publishing, Ltd. All rights reserved worldwide. Article reprint fee $500. All trademarks belong to their respective holders. "upFront.eZine," "Talking About CAD," and "On your desktop every Tuesday morning" are trademarks of upFront.eZinePublishing, Ltd. Letters to the editor may be reproduced in an edited form for clarity and brevity. Opinions expressed in letters are not necessarily shared by upFront.eZine Publishing, Ltd.