Legacy Aircraft

Thanks. And, whew! Yesterday evening I thought Asobo/MS had really screwed us over. I've invested quite a bit of time in tweaking these port-overs. So it's a relief that this seems to be an easy fix. Of course, for anyone who doesn't read this forum -- well, I pity the fool, as a great man used to say.

This does make me wonder whether some of the funky behavior we observed in some planes we tried to port was already caused by this obsolete stuff in the AIR file. I'll be paying close attention to see if the handling of some of my more marginal planes has improved for the better, relative to before the update. It might be worth revisiting some of my earlier conversion attempts that looked all right, but didn't fly properly.

I don't think it was supercharging. The Vertigo Stearman was one of the broken planes.

Before fixing this, I did have the accidental fun of doing a 700+ knot vertical climb to the edge of space in an Iris P-40E. I reckon I topped out around 100,000 feet or so, could see stars in the black sky. The plane flopped around quite a bit on re-entry, there being not much air to stabilize the plane with. I was in a hurry to try to find a fix, so I didn't take the time to glide down and land, space shuttle style. Maybe later I'll restore the old AIR file and try it.

August
 
I ran into a new problem that turned out to be linked to the above problems.

Some of my portovers that worked just fine before the update would no longer start, they would just crank for a few seconds and then stop.
After trying a few other things I deleted the obsolete and unused entries in the airfile's and they started working again :)

Thanks August for finding the aired fix for the other problems I would never have thought of trying it for this one otherwise.

If this truly doesn't have any other side effects, and I haven't noticed any so far after a couple of test flights it looks like we have a new step to perform in porting over to do.
 
A little delirium

I created this aircraft (totaly fictionnal) in 2013 from parts taken from other models (float, wings, etc).

A little French delirium in a way that allowed me to understand how to get my digital displays accepted by MSFS among other compatibility problems.
It also allowed me to manage the textures using MCX so as to get the brightnesses etc.

The upper box indicates the DME and ETE of the next waypoint of the flight plan (or the final destination in the case of direct flight), the selection of the next waypoint is made during the passage on the current waypoint.
This replaces the FsX GPS which is no longer operating under MSFS and allows you to move from POI to POI without having to search for them.

Capture-d-cran-7821.jpg


Capture-d-cran-7817.jpg



Capture-d-cran-7824.jpg


Capture-d-cran-7825.jpg


Download link:http://frenchvfr.free.fr/download.php?lng=en&pg=786&tconfig=0
 
Looks like a really cool aircraft, but my password required for the French-VR site apparently is different from the one to actually download the file?? :dizzy: It will not work. NC
 
Navy Chief said:
Looks like a really cool aircraft, but my password required for the French-VR site apparently is different from the one to actually download the file?? :dizzy: It will not work. NC
Click to expand...


The Username and Password are done for every file to download with bold characters (black or red) on the yellow line.

Here :

Username= captain

Pwd= alderaban
 
A couple of questions on some porting problems I'm having with some GAS planes

1st, Chrome. For instance the Stearman C3B has a lovely chrome prop spinner but when ported to MSFS it's a dull grey.
I figure its either a texture problem, maybe the alpha or more likely a Material Editor setting in MCX needs tweaking but I can't figure it out what.

2nd, float planes wildly bouncing around, I get this only with the Stearman S76D1 from the Super Stearman pack and the WACO UBF-2 float plane.
I know that in FSX/P3D this would usually be a contact point problem but they work fine in FSX & P3D and no amount of messing with the contact points in MSFS fixes it.
I have found that swapping out the air file from another float plane that doesn't bounce around does fix it but I only consider that as a temporary solution as other air file settings probably affect the flight dynamics.
I have stripped out all the obsolete and unused entries in the air files but it did it before doing that too.
So it must be something in the air file but I have no idea what.

Anyone have any ideas on either of these problems ?
 
Legacy Aircraft - port over of B-26

Thanks for the pointers on how to import legacy aircraft. I was able to start the import of Milton's B-26 Marauder. It flies okay with the default parameters (a bit underpowered) but I will tweak it to more realistic parameters a bit later. The exterior looks great but the cockpit needs working instruments. Very good start and certainly a work in progress. Here it is flying out of Martin State (KMTN) on a stormy night (7/1).
Milton_s_B26.PNG
 
My Two Cents Worth

G'day to everyone.

First I wish to thank everyone who provides advice, insights and assistance to those of us willing to dig into things and see what we can achieve. Without community support this hobby would be blah...

Second, I was reminded that this forum is the place to share experiences and insights with importing older models into MSFS -- I had been posting over in the Screenshot forum and was gently reminded to post here.. ;)

So, here's what I offered to others by way of my own experiences and insights:



As I've been importing some of my favorite models into MSFS, I keep discovering new challenges and things to try and understand. It seems that for every 5 I successfully bring in to the game, 5 more present odd results.

Note: Please understand that I first wish to get models into the game and flying reasonably well before tackling the more difficult challenge of configuring the cockpits.




At this point I can describe several recurring typical issues and some insights:




  1. A model converts in but has several areas which are all white (and which seem to defy any effort at alpha channel editing or texture manipulation and so I suspect must be something hard-coded in the model itself -- though still trying to understand and overcome this issue).
  2. A model converts in but acts squirrely when one attempts to fly it in the game. My temporary fix (as is the case with the above KC-97) is to replace the air file with one from another similar model which is behaving properly in the game -- an old trick well known to many here I'm sure from previous versions of the game).
  3. My discovery that one can simply use a place holder for either panel or sound folders [i.e., create a folder, add a blank panel.cfg or sound.cfg] allows one to bring the model in and see how things look/act more easily. I also do this when I see that a panel requires DLL (which are not accepted by new game and prevent models from being successfully imported). I also try to avoid importing useless gauges and panels that require too much effort to repair afterwards.
  4. Before converting, make sure to edit any changes you wish to make in the aircraft.cfg [i.e., editing information] before importing. saves frustrations afterwards.




I'm sure I've forgotten something and I will also discover new challenges but I encourage anyone to begin experimenting. I've enjoyed seeing what I can bring forward for my own enjoyment -- especially my love of vehicles and ships for further explorations of the beautiful 'world simulator' that FS has now become!

Just wanted to contribute in some small way to the growing knowledge base here.




Thank you Asobo and Microsoft for this wonderful game.


Cheers


KevinB
 
You must log in or register to reply here.
Back
Top