Request UMMU Compatible Helicopter?

this is from kev 33 dolphin

Code:
	const int nlift = 33;
	static const double AOA[nlift] = {-180*RAD,-165*RAD,-150*RAD,-135*RAD,-120*RAD,-105*RAD,-90*RAD,-75*RAD,-60*RAD,-45*RAD,-30*RAD, -25*RAD , -20*RAD , -15*RAD , -10*RAD , -5*RAD , 0*RAD , 5*RAD , 10*RAD , 15*RAD , 20*RAD , 25*RAD,  30*RAD, 60*RAD, 90*RAD, 120*RAD, 150*RAD, 165*RAD, 180*RAD };
	static const double CL[nlift]  = { -0.131 ,  -0.665,  -0.1  , -0.032 , -0.015 , -0.011 , -0.009, -0.009, -0.011, -0.02 , -0.05, 	-0.08   , -0.13   , -0.24   , -0.4    , -0.32  , -0.13 , 0.56  , 0.82   , 0.54   , 0.26   , 0.14 , 	0.081 , 0.013 , 0.008 , 0.013  , 0.062  , 0.295  , -0.132   };
	static const double CD[nlift]  = { 0.01358,0.13833 , 0.846  ,1.307   ,1.73    , 2.49   , 2.61  , 2.81  , 2.18  , 1.66  , 1.003 , 0.68    , 0.36    , 0.29    , 0.12    , 0.05   , 0.01  , 0.04  , 0.09   , 0.23   , 0.48   , 0.68 , 1.11  , 2.31  , 3.44  , 1.62   , 0.74   , 0.204  , 0.014  };
	static const double CM[nlift]  = { -0.015 , -0.008 , -0.018 , -0.027 , -0.030 , -0.033 , -0.031, -0.025, -0.017, -0.011, -0.005 , -0.00  , 0.03  , 0.003  , 0.001  , -0.00 , -0.00 , -0.001, -0.004, -0.008 , -0.011 , -0.014,  -0.018,-0.030 , -0.031,-0.017  , -0.005 , -0.003 , -0.015 };
 
Slightly strange behavior, but could work.
 
Would it be possible to replace the single rotor by a rotor disk? Eg, if rotor speed less than x rpm, display a transparent disk instead of the individual rotor blades.

From meshing point of view transparent disk should be last meshgroup in meshfile and preferably last meshgroup to render to actually see objects through it (other than planets)

If it's done as separate mesh added to vessel, then remember to make it secondary to render.

Just my :2cents:
 
like this:
nh90prop3.jpg


In the Ummuplane we just replace the prop blades with the blur the blades are too high for now
attached a new dll


Ran into an issue. Even though the material setting is set for .10 transparency I get this:
NH90PROP4.jpg


.878431 .878431 .878431 .1
.878431 .878431 .878431 .1
1 1 1 .239216 20
0 0 0 .239216
MATERIAL NH90TAIL
.878431 .878431 .878431 .1
.878431 .878431 .878431 .1
1 1 1 .239216 20
0 0 0 .239216
TEXTURES 2
NH90/nh90prop.dds
NH90/nh90prop1.dds

I use GIMP to make the white areas transparent but no luck
 

Attachments

Last edited:
Ok. I can make the white part of the texture transparent but not the blade part. I am using GIMP. any ideas?

Paint those white stripes (top right in DXTBmp view) on alpha channel ~50% Grey (R: 128 G: 128: B128 - in 8 bit notation eg full color is 255)

Also you can add a flag in "blurred mesh' " meshgroup to disable it from casting shadows when in blured state since orbiter don't support partial shadows
 
Last edited:
Thanks. This is what I have. I think the dark grey park should be darker? what if the height was smaller?

Alpha Channel
nhprop3_A-1.jpg


finished
nh90prop7-1.jpg


nh90prop8-1.jpg


FLAG 1 no shadow

new tail rotor

darker I think because of lighting. But still the dark grey park are missing
nh90prop9.jpg
 
Last edited:
Thanks GREAT
This is what I get.
nh90prop10.jpg


what did you do?

Can you do the tail rotor also. Basically the same except no yellow and a lighter gray at the end.

nhrotor.jpg
 
Last edited:
Here is an updated NH90 new blades textures, Thanks Loru!!

Used the HH64 vertical lift. Now when you press K for start up the rotors turn and then it goes to the blurred disc. Then when you shut down K the rotors appear and slow down

nh90prop11.jpg


http://www.4shared.com/zip/dicwQ9p7/NH90G.html

I had to used 4 shared as I could not attached the whole zip file
 
Can you make the blurred rotor disks a bit thinner - the side walls of the cylinders are not really needed and only take away triangles for rendering?
 
updated rotor discs mesh: resized x.25

Not thinner like that...rather make it of thickness zero, so you don't need side walls at all.

Currently modeling the PFD along the specs of the Airbus A320 PFD, I hope this doesn't disturb too much.
 
ok so no sides. But then wouldn't need 2 meshes one for each side/face. If you had a single faced mesh on one side it would look good but underneath you wouldn't see it.
 
ok so no sides. But then wouldn't need 2 meshes one for each side/face. If you had a single faced mesh on one side it would look good but underneath you wouldn't see it.

Yes, but you already have two such meshes. also you don't need two. One mesh with two sides is enough.
 
ok. I'll make a mesh with two faces/sides. Should I position in in the center of the blades? That's where the disc are now. But there will be a gap between the disc and the cap
 
ok. I'll make a mesh with two faces/sides. Should I position in in the center of the blades? That's where the disc are now. But there will be a gap between the disc and the cap

Thats OK, there are far worse graphics errors compared to reality.
 
I can't wait for finished add-on.

and maybe sugestion: Bell222
bell%20222%20016.jpg
 
Back
Top