|
Author
|
Topic: Urgently Wanted - OPS Version 1.08
|
wakeup tailgunner
Pilot
|
posted 10-12- 03:55 PM
   
This is the one that will import LOD files without mangling them. If anyone out there has a version, could you mail it to me please. I am getting fed up with workarounds! When you use .OL odd things happen to the DOF's which don't always work. Then you have to re-do them all & re-position. Then, if you need to make adjustments to a model part, you have to start again. Re-using .OL causes model parts to gradually pick up cumulative rounding errors. If I could do it any other way, I would! Cant use VRML cos I don't have Max. AC3D .WRL files don't work. Can't use LOD import with OPS 1.3. Tried lofdfix patch and it didn't. Can't seem to find a conversion process for any file type I can generate that imports the textures properly. HELP!!!!!!! IP: Logged |
Razer
Pilot
|
posted 10-12- 08:46 PM
1.03 imports LODs fine, if you want the EXE email me and i'll send it over...IP: Logged |
wakeup tailgunner
Pilot
|
posted 10-13- 03:38 AM
Whirlwind mailed me version 1.0, and it does what I need. Thanks for the offer though. OL files position everything for you, but the DOF data ends up added to the property list, and you can't edit it visually in OPS. Also, it has a habit of attaching DOF files to the child objects as well as parents. Can get very screwy!A good example is my TBM. I chanegd the model and created a new OL file. Rebuilt it, and it won't fly. It should be an SBD5 with a different shape. Nope. I would expect the DOF's to need moving, but the thing just falls out of the sky. All control surfaces move, but the properties are totally wacked. Not a major problem when you build from scratch, but when you need to change one LOD over on something like a B17...... IP: Logged |
JG3_der_Boom
Cadet
|
posted 10-21- 01:24 PM
could enyone emial me a early version off ops like v 1.0 or 1.03 just got ac3d  and ops 1.2 something ,is messy it wont import the lod file wen i save it with ac3d i would
oh and another question weni import a plane in ac3d it wont export it as a lod do i need to export evry thing from the plane as a part il thank you iff you could hlp me  ------------------
der boom IP: Logged |
jedi
Pilot
|
posted 10-21- 03:08 PM
Workaround for these problems:Copy and paste what you need (a wing, for example) from another plane. This function works right in all OPS AFAIK. Now you have an extra wing. It brings all its DOFs and properties with it from the other plane. Change these as required, and move the imported part to its correct location. Delete the original part. Save the .sm file. Now reopen the .sm file. Your imported part will be called "wing1," "wingTip1," etc. Change the part names back to the names of the original part. Save again. Now use SMD to break the model into parts, and use your 3D program to reshape the new part, working ONLY on the parts involved, NOT the whole .ol file! When finished, use OLC to rebuild the model. I haven't had any problems using this method. You can also build new parts in AC3D, export them as .lod files, i.e. newCanopy.lod. Then just replace the specific .lod file with your new .lod file. Rebuild with OLC and your new part will be there, with all the properties of the old part. Then use OPS to move the new part to its correct spot.
------------------
--jedi-- IP: Logged |
wakeup tailgunner
Pilot
|
posted 10-22- 03:03 AM
Jedi, The problem I found with the DOF was that the data ended up in the property box. This meant you could not visually check you DOF position or easily move it. This can be annoying! It can also add dof records to child objects when you don't wnat it to! run SMD and OLc on the B17 and then try using some of the gun positions! I also wanted to be able to modify individual parts without mucking around with repeats of SMD OLC which can cause cumulative misalignments of the model. I think it all depends on the order in which you do things! IP: Logged |
jedi
Pilot
|
posted 10-22- 10:35 AM
I guess I should've also added that I'm using OPS v 1.2, not 1.3x. The only thing I'll use 1.3 for is to look at the model and make hidden objects visible temporarily. Anything I save with 1.3 becomes instantly corrupted and unflyable.With the combo of 1.2 and smd/olc I've had zero problems (except for saving pilots in OPS, which is still broken, and having to sacrifice the .lod import feature). I think you can directly edit the .sm file too. All you need to know is where the lines are you want to change. Open the .sm in OPS, move your DOF, note the new coords, exit without saving, and edit the .sm file directly. Tedious tho, I know. 
------------------
--jedi-- IP: Logged | |
FSIC Messageboard
UBBFriend: Email This Page to Someone! 
