Beautiful model, Thanks to all who developed it.

 

One small thing ...... I've installed the "Aviation Partners Boeing 737-700 scimitar winglet (N162WC)" textures ( Filename:tds737_avp.zip ) but nothing shows in the sim .

 

Can anyone help please ?

 

Thanks again.

 

Pete.

The files on Avsim include the updated FDE.

 

The Delta and Southwest I included the models (and updated FDE) so you shouldn't have to change those unless you want everything in one common folder. If so, both use the 'W2' model for the winglets, no eyebrows, or the BE model for eyebrows, no winglets, or any of the above that I listed will work, really. If you were to drop those files in the base package folder, then when adding the livery [fltsim] section, change model=W2, or model=B--E, or any you want that matches with the folder. I'll post these again.

 

--E ... Eyebrow
--W1 ...Winglet which has 1 cutout for nav/strobes
--W2 ...Winglet which has cut out for nav/strobes each
--W3 ... Scimitar split winglet
--P1 ... PIP update model (Red beacon and main gear bay's edge is round)

Also there are 2 engine types, CFM56-7B and 7BE.

So there are:

CFM56-7B
CFM56-7B--E
CFM56-7B--W1
CFM56-7B--EW1
CFM56-7B--W2
CFM56-7B--EW2
CFM56-7B--W3
CFM56-7B--P1W2
CFM56-7BE--P1W2

If anyone gets a crash to desktop in the vc, it's more than likely because you have DBS Walk and Follow installed. 

 

A quick fix to try is to modify the "model=, panel=, sound=, texture=" etc. lines in the aircraft.cfg and remove all spaces before/after those parts.

Kyle,

 

Thanks for updating the FS Sites with the FDE's; for those of us who don't use FB it works much better.

 

Folks... let's keep this Thread rolling with tips, tricks and tweaks for this wonderful, new offering from the folks at TDS! If the 787 thread was any indication, this one can be as useful and helpful to all as the other one was.

 

No one's passing more 411 on these birds than here on AVSIM, and where else is one of the TDS Team offering help... so keep it up.

 

If you've got issues, post them here and we'll see if we can help.

 

Remember... no sour grapes, or "why do we need another 737" comments; if you don't like the offering, well... sorry to hear that.

 

Hi,

 

many thanks for your effort to bring this plane to the community! (Of course we need it, it's my first 737 ^_^ )

Can you recommend an appropriate sound set?

 

Harald

If anyone gets a crash to desktop in the vc, it's more than likely because you have DBS Walk and Follow installed. 

 

A quick fix to try is to modify the "model=, panel=, sound=, texture=" etc. lines in the aircraft.cfg and remove all spaces before/after those parts.

Afraid not... I'm assuming this applies only to the [fltsim.x] section, and not all the other unusual stuff strewn all over the aircraft.cfg file?

I have removed spaces around "=" and still get a CTD the instant I switch to VC view.

[fltsim.0]

title=FREEWARE_©_TDS_16AUG2013_737_CFM56-7B--W3_+A7000_+D00_+B0 ?? //Replace ?? with airline/aircraft variant, Do NOT remove anything else.

sim=TDSBoeing737-700w //Do Not Edit

model=B--W3

panel=

sound=

texture= 

kb_checklists=

kb_reference=

atc_id=N711SY

atc_id_color=

atc_parking_types=gate

atc_parking_code=

atc_airline=Sun Country

atc_flight_number=884

ui_manufacturer=Boeing

ui_type=737 TDS

ui_variation=BBJ

description=Boeing 737NG BBJ 

visual_damage=

 

It would be a great shame if DBS W+F were conflicting, because of course that would mean the 737 is off the HDD and part of a non-SDK-compliant bit of history.

 

Hope it can get sorted.

Try

title =FREEWARE.......

I have made some fixes and so far, people testing them are reporting the crashing completely fixed. I'll have a few more test/report back and I will upload fixes for all of my uploads including the 737-700 main base package.

Fixes uploaded to the library....................

The fix was needing to remove any of the // lines after title= and sim= and also remove the spaces before/after those = .

For example, the aircraft.cfg entries must follow this format, changing only the necessary text for your livery and antenna/decal options:
 

// WARNING NEVER TAKE OFF "FREEWARE_©_TDS_16AUG2013" from title= -------------------------

// If you do those , wings will be gone and other unexpected things will happen. |

// Title must be under 127 character since FSX will cause error when exceed. |

// If you have any problems please find our Facebook Group Support Page at |

// https://www.facebook.com/groups/TDS.SkySpirit.B737NG/ |

// |

// +A ... Option Antenna |

// +D ... Option Decal |

// +B ... Option Beacon Position |

// |

// Number after Above is Hex and checks at Bit |

//0 = 0000 | DO NOT REMOVE ANYTHING

//1 = 0001 | BETWEEN THESE BRACKETS

//2 = 0010 |---- THIS IS INFO FOR OUR

//3 = 0011 | SECURITY CODES AND MODEL

//4 = 0100 | OPTIONS.

//5 = 0101 |

//6 = 0110 |

//7 = 0111 |

//8 = 1000 |

//9 = 1001 |

//A = 1010 |

//B = 1011 |

//C = 1100 |

//D = 1101 |

//E = 1110 |

//F = 1111 ------------------------|

 

[fltsim.0]

title=FREEWARE_©_TDS_16AUG2013_737_CFM56-7B--W2_+A3000_+D00_+B0_BASE_WHITE

sim=TDSBoeing737-700w

model=B--W2

panel=

sound=

texture=

kb_checklists=Boeing737-800_check

kb_reference=Boeing737-800_ref

 

atc_id=N645AS

atc_airline=Alaska

atc_flight_number=884

atc_heavy=0

atc_parking_types=GATE, RAMP, CARGO

atc_parking_code=ASA

 

ui_manufacturer=TDS

ui_type=737-700

ui_variation=White - B--W2

visual_damage=1

description=TDS - Boeing 737-700\nVersion - FDE Version 2004.9.3\n\nModel Designer\n   Hiroshi Igami\n\nFlight Dynamics/Scenario/Effects Designer\n   Warren C. Daniel\n\nMaster Texture Designer\n   Kyle Schurb\n\nTest Pilots\n   TDS Members\n\nMaximun Range: \n   3,383 nautical miles

Thanks for the follow-up, Kyle.

Sure thing.

One more livery (maybe last one) from me, before moving onto the -800s:

And I've just merged it with the iFly panel. It. Simply. Rocks :biggrin: I had to move the empty CG 15ft forward, but handling doesn't seem to be affected using iFly FDE, thanks a lot for your hard work.

 

I have two questions:

1) Will the other versions be modeled? (specially the -800 and the -900ER)

2) In the base pack I find various model codes, but I can't figure them out. Which code means which variation? (winglets/eyebrows/anything else)

Do you have any problems have the aircraft holding the cruise altitude? And would you mind if I can try out your merge?

Do you have any problems have the aircraft holding the cruise altitude? And would you mind if I can try out your merge?

 

Not at all regarding this. Sadly, I've just figured that, by merging iFly's panel and FDE with TDS model, I've messed up the iFly 737-700 (iFly model) and I have no hydraulics anymore (no rudder, no ailerons, no elevators).

 

But if you insist, just copy iFly's 73G airfile and aircraft.cfg. In the CFG replace all aesthetic sections (exits, lights, contact points, effects and fltsim.x) with the TDS values. In the Weight and Balance section, make sure this line is this way:

empty_weight_CG_position     =  15, 0, 0  

I have to check what makes iFly go nuts when merging, and if there is a way to prevent this. Or if there is nothing to do, but having to decide between a VC and advanced ground animations.

Not at all regarding this. Sadly, I've just figured that, by merging iFly's panel and FDE with TDS model, I've messed up the iFly 737-700 (iFly model) and I have no hydraulics anymore (no rudder, no ailerons, no elevators).

 

But if you insist, just copy iFly's 73G airfile and aircraft.cfg. In the CFG replace all aesthetic sections (exits, lights, contact points, effects and fltsim.x) with the TDS values. In the Weight and Balance section, make sure this line is this way:

empty_weight_CG_position     =  15, 0, 0  

I have to check what makes iFly go nuts when merging, and if there is a way to prevent this. Or if there is nothing to do, but having to decide between a VC and advanced ground animations.

 

Thanks for the tips and the heads up on iFly going bonkers. Do you think maybe you could have gotten the aircraft.cfg files mixed up? I have done that before with merges and it is not fun. Hope you get it straightened out.

Thanks for the tips and the heads up on iFly going bonkers. Do you think maybe you could have gotten the aircraft.cfg files mixed up? I have done that before with merges and it is not fun. Hope you get it straightened out.

 

I don't think it's about the FDE, but something else gauge related. The funny thing is that the TDS/iFly merge worked beautifully; the iFly native model went nuts. The opposite should be the right thing to happen. Anything, the merge deserves its very own thread, let's not hijack this one.