|
Author
|
Topic: OPS Beta bug?
|
jedi
Pilot
|
posted 07-29- 09:48 PM
   
Was doing some work on Tailslide's beta 190A4 to straighten out the wings. Initially replaced all the .lods with models re-oriented in AC-3D, so as not to affect the airfoils. Everything A-OK in the sim. Then, I had to move the bomb pylons and gun barrels a little in OPS. Suddenly the plane is unflyable--acts like it's just had its rear fuselage shot off, just waffles to the ground.So I thought maybe I accidentally moved an airfoil or something. Took the original 190 Tail sent me (verified functioning normally in the sim) and then just move ONE gun barrel, a tiny amount. Saved the .sm file in OPS--whammo! Unflyable in the sim. Then I took my finished 190, opened it up in the "production" version of OPS, changed all sorts of stuff, added a sliding canopy, moved cockpit parts around, and saved it. And it flew just fine. So, no clue what the problem is, and I did most of the work on the Dam Buster Lanc using the beta OPS version, so I'm stumped on this one. Guess I'll stick to the normal OPS version for now tho.
------------------
--jedi-- IP: Logged |
Laika 801
Pilot
|
posted 07-30- 03:19 AM
Jedi ? Test if the pilots parachute still works in the unflyable 190.
If the chute does not work (I hope it is that) then the airfoil of the chute is activated = the pilot.sm file is crushed.If this is the reason - make sure to check "do not save referenced files" in the save dialog. Or if you changed a reference file, and need to save it - uncheck "parse proplist" in OPS. Or just replace the buggish pilot.sm with a new one. But - wait, I think the 190 does not come with an extra pilot.sm - so it might be something else. LK IP: Logged |
Laika 801
Pilot
|
posted 07-30- 03:26 AM
Hmm - I looked at the .sm file, it uses the LilgPilot.sm.
Jedi - please check if you got this file in your pilot folder, if it is not there, then it is something else...
LK
IP: Logged |
Bryan Russell
Pilot
|
posted 07-30- 08:44 AM
There is something about the way some some phyCG lines are formatted that OPS didn't like. This would definitly screw the FM.I thought I had fixed that in the latest, maybe not, or maybe another similar thing. The best bet is to do as Laika says and turn off the proplist parsing. Movement will still work, only the proplist editing using the panel won't. IP: Logged |
jedi
Pilot
|
posted 07-30- 02:09 PM
Not sure I followed all that. I do have the Lilgpilotsit.sm in my pilot folder, but he appears to be "unharmed," i.e. the new, working 190A4 saved in OPS 1.2.1 flies just fine and the pilot bails out properly, still attached to his chute, which seems to work.I disabled the "save referenced files" feature, but the plane is still unflyable. The pilot functions normally tho. If I uncheck "parse proplists," does that mean I can't edit the properties in OPS? That's one of the most useful features  I think I'll stick with 1.2.1 for now. Oh, another thing I noticed: you can't rename the texture files in OPS beta. Everything else you can rename by clicking on it, but the texture files' names can't be edited.
------------------
--jedi-- IP: Logged |
ArgonV
Pilot
|
posted 07-30- 02:22 PM
I use OPS 1.21 and 1.30 Only major problems I have are the dissappearing DOFs when an object is rotated and OPS freezing up my computer when Im zoomed in too close and I rotate the object around. (this happens on both versions of OPS I use) Also, in OPS 1.30 you cant copy shadows (or any other thing that is in the top i.e. not in the main aircraft) back and fourth to other SM files (try copying a shadow using OPS 1.30 and pasting it into another SM file... Im pretty sure it will crash on you) I had this problem when making my Mistel so I had to use OPS 1.21 for that.IP: Logged |
Laika 801
Pilot
|
posted 07-30- 05:19 PM
jedi - you can rename the textures, double click on one and change the name. then go back, click on any object (and switch to the parts-tab) and svae/reload. Now the texture name is changed...the other thing with the 190 is really strangeArgonV - copying shadows and other things from "above" is no problem in OPS1.3B just uncheck "use base model" and it works fine (tested it 2 mins ago to be sure). Yeah V1.3B is a bit unstable, but works good for me so far...Bryan, it was often said, but I say it again - Thanks for giving us OPS. I would love to see a new version, with less "new" things but a bit more stable, would make it easier to work with. LK
IP: Logged | |
FSIC Messageboard
UBBFriend: Email This Page to Someone! 
