The download hangar is currently disabled. We're doing our best to bring it back as soon as possible.
Wish list for conversion to FSX/P3D
Wish list for conversion to FSX/P3D
I don't see that anyone else has started a wishlist for conversion to FSX/P3Dv4. I'm using P3Dv4.1 and the following (amongst many others) are missing their undercarriages..
C-17s
C-130s
Got another favorite you'd like to see upgraded? If so, add a comment...
Thanks to all for their hard work on these aircraft that makes our hobby so enjoyable!
C-17s
C-130s
Got another favorite you'd like to see upgraded? If so, add a comment...
Thanks to all for their hard work on these aircraft that makes our hobby so enjoyable!
Re: Wish list for conversion to FSX/P3D
The HTAI C-130's have been converted. You can find them over at the AIG forums.
Re: Wish list for conversion to FSX/P3D
RE C-17
They are PAI models and I don't know if MAIW has the rights to the model.
I did look at converting them for my own use and they need major re-building. The reverse thrusters are broken in conversion and will need to be re-modeled from scratch.
Gavin
They are PAI models and I don't know if MAIW has the rights to the model.
I did look at converting them for my own use and they need major re-building. The reverse thrusters are broken in conversion and will need to be re-modeled from scratch.
Gavin
Re: Wish list for conversion to FSX/P3D
C-130's
They are also available here in our Download Hangar: link.
A full conversion package with all the repaints from the MAIW packages is coming soon.
C-17
Actually, the model was created by Rysiek Winawer, the same guy who created the RWAI A-10 and an (inactive) MAIW contributor. He gave PAI the rights to use his model, as he did to us. And since he's given us permission to convert his A-10A to an A-10C before, I don't see why he wouldn't allow us to convert his C-17. If you're interested, Gavin, we can try to contact him to make sure.
They are also available here in our Download Hangar: link.
A full conversion package with all the repaints from the MAIW packages is coming soon.
C-17
Actually, the model was created by Rysiek Winawer, the same guy who created the RWAI A-10 and an (inactive) MAIW contributor. He gave PAI the rights to use his model, as he did to us. And since he's given us permission to convert his A-10A to an A-10C before, I don't see why he wouldn't allow us to convert his C-17. If you're interested, Gavin, we can try to contact him to make sure.
Re: Wish list for conversion to FSX/P3D
Greg: Since KCHS in Charleston is my "home base" I'd love to see the C-17s that are based here looking as good as possible. So, please do inquire about converting the C-17s. Thanks.
- gsnde
- MAIW Admin
- Posts: 4381
- Joined: 05 Apr 2007, 08:13
- Version: P3D
- Location: South-West Germany
- Contact:
Re: Wish list for conversion to FSX/P3D
Greg, we have the allowance from Rysiek to do with his models whatever we think appropriate.
From mobile hence short
From mobile hence short
Cheers,
Martin
________________________________________
The Owl's Nest * Military Aircraft Reference * ICAO Reference * Distance Calculator * MAIW, Military AI & UKMil Reference
Martin
________________________________________
The Owl's Nest * Military Aircraft Reference * ICAO Reference * Distance Calculator * MAIW, Military AI & UKMil Reference
Re: Wish list for conversion to FSX/P3D
Gavin: I just converted the model with the latest development version of MCX and all animations are OK. I guess the zero keyframes from the reverser animations were missing, previous MCX builds could not handle that. I only did a quick conversion of the highest LOD, if you want to have it please let me know.
Henk Schuitemaker.
Henk Schuitemaker.
Re: Wish list for conversion to FSX/P3D
Hi Henk,hschuit wrote: ↑23 Jan 2018, 13:45 Gavin: I just converted the model with the latest development version of MCX and all animations are OK. I guess the zero keyframes from the reverser animations were missing, previous MCX builds could not handle that. I only did a quick conversion of the highest LOD, if you want to have it please let me know.
Henk Schuitemaker.
that is good news, I hadn't gone back to revisit the model for a while.
If you could share it with me that would be great, with the recent testing about the value of LODs I could probably do something with your high LOD conversion and a couple of the lower LODs without animation. I'll PM you an email address.
And to the rest of the world - please don't pester me about when it will be converted, I will do it as and when I have time
Gavin
Re: Wish list for conversion to FSX/P3D
As we have some conversion experts, a few questions if I may (looking at converting our new F-16's to FSX) ....
1) How do you deal with tick18 animations?
Remove Before Flight flags, pilots head etc all use tick18 to drive them. When I pull the mdl file into modelconverterx the tick18 animations aren't listed in the Animation Manager.
I can assign a dud name to the parts in FSDS and recompile, they then show up as userdefined in the Animation Manager, so thats a workaround.
2) Ambient - it is my understanding that ALL Ambient tagged parts MUST use the same number of keyframes?
3) Heirarchy on visibility polys - We know modelconverterx doesn't pull the visibility code.
I tried assigning FSX code to the parent poly in the Heirarchy Manager and the connected parts didn't appear/disappear when triggerred.
Of course the preferred method would be to actually convert the original FSDS file, but this has some major problems.
When compiled for FSX all the animations are screwed.
Looks like I would need to use a parent poly for eveyone of them, and that is just too much work.
Exhausts alone have 36 parts for the GE, and 45 parts for the P&W versions.
1) How do you deal with tick18 animations?
Remove Before Flight flags, pilots head etc all use tick18 to drive them. When I pull the mdl file into modelconverterx the tick18 animations aren't listed in the Animation Manager.
I can assign a dud name to the parts in FSDS and recompile, they then show up as userdefined in the Animation Manager, so thats a workaround.
2) Ambient - it is my understanding that ALL Ambient tagged parts MUST use the same number of keyframes?
3) Heirarchy on visibility polys - We know modelconverterx doesn't pull the visibility code.
I tried assigning FSX code to the parent poly in the Heirarchy Manager and the connected parts didn't appear/disappear when triggerred.
Of course the preferred method would be to actually convert the original FSDS file, but this has some major problems.
When compiled for FSX all the animations are screwed.
Looks like I would need to use a parent poly for eveyone of them, and that is just too much work.
Exhausts alone have 36 parts for the GE, and 45 parts for the P&W versions.
-
- Cadet
- Posts: 1
- Joined: 18 Feb 2011, 20:33
- Version: FS9
Re: Wish list for conversion to FSX/P3D
North east ANG bases (Niagara)
Re: Wish list for conversion to FSX/P3D
Weescotty, I am not familiar with FSDS, no clue what tick18 is... For the pilot/ground eqt visibility in FSX I use the nav or beacon light state. Example:
Can't answer the question about Ambient tags. Also I do not recognize the issue with hierarchy on visibility polys. I use the latest development version of MCX, afaik if parent modelparts have a visiblity tag, the child parts do not need one.
Code: Select all
(A:LIGHT BEACON,bool) ! (A:VELOCITY BODY Z,knots) 1 < and if{ 100 } els{ 0 }
Re: Wish list for conversion to FSX/P3D
I really don't know how this fits in with this thread.
Steve
_______________________________________________________
Quid Si Coelum Ruat
_______________________________________________________
_______________________________________________________
Quid Si Coelum Ruat
_______________________________________________________
Re: Wish list for conversion to FSX/P3D
Re: Wish list for conversion to FSX/P3D
Weescotty, I use Ambient animations as a replacement for tick18 for things like pilots heads that need to move on a regular basis. There are multiple Ambient variables (6 off the top of my head) so that you can have different animations. Like Henk I use visibility conditions based on ground speed and light state to display ground equipment, flags, pilots etc.
Pull the HTAI F-16 conversion into MCX and you can see what I did with Ambient and visibility conditions to control the pilot visibility and head movement. I don't know if it is the best way (or even the right way) but it is a start.
Hope this helps a bit
Gavin
Pull the HTAI F-16 conversion into MCX and you can see what I did with Ambient and visibility conditions to control the pilot visibility and head movement. I don't know if it is the best way (or even the right way) but it is a start.
Hope this helps a bit
Gavin
Re: Wish list for conversion to FSX/P3D
Ahhh now I see.
OK I will answer, briefly, to get this thread back on track.
1. This thread is about aircraft conversion.
2. We have never done a NE ANG pack so we can't convert it.
3. We have never done any scenery for Niagara Falls International Airport. An afcad yes, but no scenery.
Steve
_______________________________________________________
Quid Si Coelum Ruat
_______________________________________________________
_______________________________________________________
Quid Si Coelum Ruat
_______________________________________________________
Re: Wish list for conversion to FSX/P3D
Thanks for the replies...
Something is up!
The hierarchy for the flags / chocks etc just isn't there.
Even tried adding the hide code to a cap that had a flag as its child.....
Cap disappears, flag remains.
Ambient - think I need to change the key frames from 0 -> 60 to 0 - 100
No real maximum, but I think it's 100 minimum.
Something is up!
The hierarchy for the flags / chocks etc just isn't there.
Even tried adding the hide code to a cap that had a flag as its child.....
Cap disappears, flag remains.
Ambient - think I need to change the key frames from 0 -> 60 to 0 - 100
No real maximum, but I think it's 100 minimum.
Re: Wish list for conversion to FSX/P3D
Did a little playing with it the last few days.....
Tick18 animations - Do not show up in the Animation Editor with FS2004 compiled mdl files- access to the original FSDS allows the tick18 parts to be renamed to a junk part name. Once recompiled they show up as userdefined8 in the Animation Editor.
Maybe as a result of that, or because covers, flags etc all link to a visibility poly the hierarchy is lost. You have to go through each LOD and select each part in the Heirarchy Editor, and set them to your XML.
Takes around 1 to 1.5 hours per model. Lot of work.
Tick18 animations - Do not show up in the Animation Editor with FS2004 compiled mdl files- access to the original FSDS allows the tick18 parts to be renamed to a junk part name. Once recompiled they show up as userdefined8 in the Animation Editor.
Maybe as a result of that, or because covers, flags etc all link to a visibility poly the hierarchy is lost. You have to go through each LOD and select each part in the Heirarchy Editor, and set them to your XML.
Takes around 1 to 1.5 hours per model. Lot of work.
Re: Wish list for conversion to FSX/P3D
Ugh....
-Mike G.
Recovering flight sim addict, constant lurker.
Check out my real life RV-8 build here: RV-8 Builder Log
Recovering flight sim addict, constant lurker.
Check out my real life RV-8 build here: RV-8 Builder Log
- John Young
- MAIW Developer
- Posts: 4226
- Joined: 12 Jul 2008, 15:15
Re: Wish list for conversion to FSX/P3D
Better than conversion in Gmax. That's 4-6 hours per model depending on whether props are a feature. They have 6 tags per prop to apply.
John
John
C-17 conversion light question
Hi,
thanks to Henks advice I am making slow headway on the C-17 conversions.
I have one question about the lights. Does anyone know which lights are used for taxi-ing? The UKMIL C-17 has lights on the nose gear that are set up as taxi lights but all the videos I have seen only show the wingtip lights and the lights on the front fuselage. I found a USAF C-17 Operations Procedure manual and it refers to a "nose landing light" and "nose taxi light". It states that at least "One wingtim or nose landing light on each side will be operational". With reference to the nose taxi light it states "One may be inop provided the nose landing light on the same side is operational".
I am assuming that these "nose" lights are the lights on the forward fuselage.
thanks
Gavin
thanks to Henks advice I am making slow headway on the C-17 conversions.
I have one question about the lights. Does anyone know which lights are used for taxi-ing? The UKMIL C-17 has lights on the nose gear that are set up as taxi lights but all the videos I have seen only show the wingtip lights and the lights on the front fuselage. I found a USAF C-17 Operations Procedure manual and it refers to a "nose landing light" and "nose taxi light". It states that at least "One wingtim or nose landing light on each side will be operational". With reference to the nose taxi light it states "One may be inop provided the nose landing light on the same side is operational".
I am assuming that these "nose" lights are the lights on the forward fuselage.
thanks
Gavin