|
Author
|
Topic: OPS question WRL import
|
Tailslide
Pilot
|
posted 06-13- 10:57 PM
   
I want to try a terrain.. but all the terrain objects are named tundra#1 etc.. how can I import this from .wrl when the # character is reserved as a comment character in the .wrl format? TS ------------------
Patch It! TS Aircombat
IP: Logged |
Tailslide
Pilot
|
posted 06-13- 11:03 PM
nevermind.. hippies OL tool and wordpad's search and replace to the rescue !IP: Logged |
Tailslide
Pilot
|
posted 06-13- 11:09 PM
Can OLC handle terrain files? It just sort of goes away and never comes back on me.
IP: Logged |
Tailslide
Pilot
|
posted 06-13- 11:38 PM
I give up.. olc wont compile the terrains, OPS gives me a blank requester if I try to use .wrl, and if I use .obj to import it page faults on me.IP: Logged |
Bryan Russell
Pilot
|
posted 06-14- 12:40 AM
Try the LOD plugin. It won't work either but at least you will have the full set  There are two things you can do though. If you don't mind importing things one at a time, the name matching isn't in effect if you select the object in OPS and then only select one object from the import box. So you can call it anything you want in MAX and then import it like that. Secondly, I would probably not be too hard to do something in OPS so that you could use a different character in the name and have OPS replace it with the '#'. [This message has been edited by Bryan Russell (edited 06-14-2000).] IP: Logged |
Tailslide
Pilot
|
posted 06-14- 12:44 AM
I can't go from Max to LOD so yes, I'm officially screwed.  I did manage to get some .wrls to import but I'm not sure what I did to the object to make it start working. Reset transform,etc didn't help. I have the grand canyon broken down into 20x20 tiles the next interesting part will be to figure out how to seamlessly map all those files.. TS
[This message has been edited by Tailslide (edited 06-14-2000).] IP: Logged |
Tailslide
Pilot
|
posted 06-14- 01:19 AM
OK I figured it out.. it works ok if I import a .wrl into OPS, save and then exit. But if I try to import another .wrl without exiting the requester comes up blank. Problem #2.. my terrain pieces come in, look good and are lined up ! As soon as I hit save and reload, they move all the way across the map to an entirely different position where they are not lined up with each other. Going into move part mode immediately after import and moving any of the pieces will also instantly teleport them across the map. TS IP: Logged |
Bryan Russell
Pilot
|
posted 06-14- 01:51 AM
I'll look at the multiple import thing. It worked fine for me.For the second, I was pretty sure I had fixed up the positioning system. It worked OK for me, before and after a reload. Is it OK to send me the WRL to look at? The reason it moves a lot when you try to move it is becuase of the scale. I havn't got the move distance quite right with regard to the distance from the camera. It should be a simepl matter of correction for perspective but it isn't. It worked OK for aircraft so I didn't do much further work on it. IP: Logged |
Tailslide
Pilot
|
posted 06-14- 10:30 AM
Bryan, when I go into move part mode and use control-arrow key once to move it a small amount it sends the piece all the way to the other side of the map (the same place it moves to when you just click save and reload). It's like there is some postition information that is not getting updated by the import. I wiped most of my terrain files, sorry. Maybe its related to the problems in the dashboard and yak wrl files I sent. Would it be possible to make the .obj import not crash when there are a large number of objects (400)? My best bet may be to make my tiles the same size as the existing terrain and turn off positioning. TS [This message has been edited by Tailslide (edited 06-14-2000).] IP: Logged |
Hippie
Pilot
|
posted 06-15- 05:38 AM
SMD and OLC should be able to handle
terrain files OK. I rebuilt dover from
a .OL file and LODS and it completed OK
on my system. BUT the .SM file produced
was incorrect!!!! There seems to be a
bug in OLC where it won't fseek and write
past a certain point in a larger file so the
groups lengths don't get properly set toward
the end of processing a terrain file!It seems to be a size thing because I've
never seen this with the smaller aircraft .SM
files. I'm investigating further, it may be a problem
with the Cygwin libraries and compiler. Hippie. IP: Logged |
FSIC Messageboard
UBBFriend: Email This Page to Someone! 
