Angel Aircraft Project Questions

[Travis]

So I've been working on the Angel, and I'm stuck with a few questions I really couldn't figure out by myself.

First: Why do the wings have differing reflections?



Second: Why do the props have different shading/densities?



Third: Why are the polys missing inside those highlighted areas?

[Fr. Bill]

FS9's MakeMDL.exe will collapse any vertices in an "interior model" that're 4mm or less in separation...

...IOW all veritices in parts must be >4.0 mm apart.

The "exterior model" has a 1mm threshold...  ::)

There are some "tricks" to work around the issue. Search the "FSDS forum" at http://freeflightdesign.com for details.

"VC Rain" modeling is described in the "Textures" forum as well as the "FSDS" forum, and there is a least one tutorial posted in the "Tutorials" forum.

[Travis]

Thanks, Bill.

[HarvesteR]

just by looking at the code, i would guess you'd have to change the minimum and maximum rotation values to negative and possibly every other part in which these values appear

Code: Select all

<Rotate>
 <Value Minimum="3" Maximum="35">(A:Prop1 RPM,RPM) 100/> <-- possibly here
</Value>
- <Failures>
 <SYSTEM_ENGINE Action="0" />
 </Failures>
- <Nonlinearity>
 <Item Value="5" X="23" Y="96" /> <-- and here
 <Item Value="35" X="116" Y="107" /> <-- and here too
 </Nonlinearity>
 <Delay DegreesPerSecond="15" />
 </Rotate>
 </Element>
- <Mouse>


i don't know much about gauge programming, but i would guess that these entries are those that control the movement of the needle, right now the inversed prop rotation might be pushing them past their minimum value, so the gauge will stay still at 0, so by inversing the rotation values of the gauge, they might work correctly again... (maybe)

i'd backup that file and then go making controlled changes and noting their effects in FS, so that when you get it to work you'll know what you did

BTW, there is a 'refresh aircraft' command in the control assignment list, which is unmapped by default... map that to a key and you won't have to reload FS every time you make a change

hope this helps

Cheers

EDIT: one more possibility i just saw, and which actually seems more correct is changing the Prop1 RPM parameter there to -(prop1 RPM) or something like that... you're inversing the value of the prop rotation, so that it passes a corrected number to the gauge... of course, you should leave all other values untouched when you try changing this one

Code: Select all

<Rotate>
 <Value Minimum="3" Maximum="35">(A:-(Prop1 RPM),RPM) 100/> <-- here (the A:Prop1 RPM bit)


i don't know much about XML syntax as well, so those parenthesis might not work well, so you could try without them as well