Legacy Aircraft

Anyone know what might be happening here with the textures? They all seem to be DXT5 .dds files, but I can't seem to get them to display properly. I am an extreme novice at this sort of thing so please forgive me if the answer is an obvious one.

Aircraft Factory P-51H

2MNtdvP.jpg
 
So, I'm more than a bit stumped guys. I have an mdl file I'd like to convert to gltf for fs2020 ( ok, I have a bunch of them ) but every time I try to use a converter I end up with an error regardless of the converter I use. Worse, it just says theres an error.. It doesnt give details.. I could use a clue and some advice..The aircraft all work in FSX and all versions of P3D through V5..
 
warchild said:
So, I'm more than a bit stumped guys. I have an mdl file I'd like to convert to gltf for fs2020 ( ok, I have a bunch of them ) but every time I try to use a converter I end up with an error regardless of the converter I use. Worse, it just says theres an error.. It doesnt give details.. I could use a clue and some advice..The aircraft all work in FSX and all versions of P3D through V5..
Click to expand...
At the moment the process of converting to glTF format is quite laborious especially when working from am MDL as all exporters cannot export animations. So we have to export to some other format like DAE or FBX then redo all the animations and hookups to the modeldef file and export to glTF.
Then we take that into MSFS via the packagetool and it will do some crunching to the file as well.
If you have the original 3D sources it's a bit easier as all the animations and naming is done so you just need to redo the textures.
 
OzWookiee said:
At the moment the process of converting to glTF format is quite laborious especially when working from am MDL as all exporters cannot export animations. So we have to export to some other format like DAE or FBX then redo all the animations and hookups to the modeldef file and export to glTF.
Then we take that into MSFS via the packagetool and it will do some crunching to the file as well.
If you have the original 3D sources it's a bit easier as all the animations and naming is done so you just need to redo the textures.
Click to expand...

No.. No. I dont have the original Source files.. That was Roberts world. I was just a number cruncher so I never needed them. He made the candy look wonderful, and I and Paul made it fly..
 
keithb77 said:
Latest Development release of MCX reportedly supports gITF - see here
Click to expand...

I assume that therefore means we can use MCX to (gonna have to change the name) to read MSFS models and paints, and can therefore use it to help test repaints?

It's not so bad using the Hangar, but it's a lot of clicks, having to change liveries and back again, switch to "airplane" mode, check it out, make a change, go through that process again... (especially when you're moving a mouse across a 55" screen back and forth between opposite corners (for some reason F12 doesn't bring up the Liveries option, I'll have to check my key bindings).

Took me 24 hours to create that C-152 repaint, back and forth, back and forth, "where's this section?"; I should notate my template so I know where all the various pieces are in the future... what a mess of a layout.

(P.S. I hate it when layouts "save space" by using reflected textures on both sides. It worked out ok on this one, except for one tiny little place, there's only a few locations reflected on this model (under the rear window, the door hinge screw covers, the doors a couple of others), but I could see it being a problem for some possibilities for this model).
 
warchild said:
Could someone help bring Mine and Roberts P-61s into MSFS?? I couldnt understand what needed to be done to do it..
Pam..
Click to expand...

It's all in the wrist Pam :) Flies well and all instruments working as they should be after conversion. Not native gLTF format but a port from the MDL file. Can't distribute for obvious reasons, but I'm sure Robert won't mind you having a copy if nobody's already done it for you?

attachment.php
 

Attachments

  • SoH P61.jpg
    SoH P61.jpg
    37.5 KB · Views: 1,142
@DC
I spoke with him the other night. I cant go into details though, but he does know i'm seeking to convert the old model and seems to be ok with it as he has zero interest in ms2020. So, A gentleman here who will also be helping me correct the flight model should it need it, made a basic port over of the mdl. and I installed it. It didnt run.
Last night he and I got together on discord and I shared my scren with him and we went through the installation. Turns out, My Game Pass installation was using directories that didnt even exist in his store bought version of the premium deluxe version.This told us that there are three separate versions of the game being installed. The Game Pass version can only be upgraded and the Premium Deluxe version upgrade for Game Pass is 89.00 dollars and contains a reduced number of aircraft and scenery's. It installs primarily in app data and a folder called wpsystem. The community folder is in app data. Store bought [rmium deluxe I believe installs where you tell it too.. and doesnt use one of the folders that the game pass version uses ( as we discovered last night. ). That was tellng as my game pass version placed a copy of the plane in a place that didnt exist for my friend. However, Fully converted liveries and aircraft do work, as I discovered by both aircraft and liveries I downloaded from FSAddon. It's only non-converted models that dont work.
Now; I want my babies in game. I want the P-61Bs and the P-61C's and the RF-61 and the Goose and the Optica, and several others I spent years with developing their flight models. I dont really care for a 787 and well, I'm sorry, I dont like Airbus. So I was faced with one of two choices. I could trash the entire Premium Deluxe Upgrade version of FS2020 and go back to X-Plane, never to see my babies again, Or I could trash the Premium Deluxe Upgrade version and buy the full Premium Deluxe version from Microsoft Store.
I miss my babies.
I bought the full Version, even though it will put me into some hardship for the next couple of months.. It should be finished installing by tonight, and then we'll try again..

P.S. So that rumors dont get started: No, Robert has not given me permission to release and distribute an MS2020 version of Our P-61 and I respect that. Should he ever give me permission then I will, since we made a promise to the good people of SOH back in 2010 to do so.

P.P.S. @DC, Your pics make me homesick ::LOL::: Maybe by tomorrow.. If not, I may be hitting you up for the port.
 
If you have the FSX SDK (which is downloadable) you can use MCX to convert P3D MDLs to FSX.

The Auster is really nice, the radio even displays correctly - the only FSX import I've seen doing that!

And the GAS Stearman demo imports well too :)
 
Beautiful! So hopeful we will get back lots of so important and valuable aircraft gems - but looking at this I am very optimistic!
 
Manfred, I think this was one of your favourites...
Unfortunately only half the instruments work and no VTOL but it looks good (better than P3DV5...)


Click for bigger picture :) (Can't upload images to SOH again?)
Cheers
Keith
 
I am new to this, and jumped in the deep.

I converted a FSX Native plane
I used the MSFSLEGACYImporter (latest version).
Except for the navigation gauges (VOR) and radios, all gauges are working.
Breaks, flaps and gear are working fine as well, but...

none of the switches are functional (no working click spots). I can't even get the lights to turn on.

Is this a known issue, or is there something I am missing?
I watched a few youtube videos, but none show nor mention the switches in the cockpit.

Any reply would be highly appreciated.
 
You must log in or register to reply here.
Back
Top