Request UMMU Compatible Helicopter?

[Urwumpe]

I wonder if you could attach a UMMU and use their HUD. But you wouldn't be able to control the copter without switching.

Would not really help much I would say. What about making a rectangle in front of the "camera" and move it with the camera?

 

[gattispilot]

But how would the data be displayed? I wonder if make it on a transparent rectangle like a MFD.

 

[Urwumpe]

But how would the data be displayed? I wonder if make it on a transparent rectangle like a MFD.

AFAIR, you only need texture coordinates again for the HUD and it again needs to be a rectangle.

 

[gattispilot]

So we need a rectangle, what size? How would the and what data would be on it.

 

[Urwumpe]

Nothing special... just a blank rectangle with texture coordinates, so orbiter can map its HUD texture on it. Data is standard HUD modes... you could make special HUD modes for hover flight if needed.

 

[gattispilot]

Ok. But still not sure how to get the HUD to display on the rectangle

Nothing special... just a blank rectangle with texture coordinates, so orbiter can map its HUD texture on it. Data is standard HUD modes... you could make special HUD modes for hover flight if needed.

 

[Urwumpe]

Ok. But still not sure how to get the HUD to display on the rectangle

OrbiterAPI documentation could provide insights.

 

[gattispilot]

here is in the APIguide:
1.12.7 Defining the HUD in the virtual cockpit
< to be completed >

Here is the latest NH90 meshes and dll. It had a VC and 2 mfd

Now a HUD

 

[gattispilot]

Here are some new images and zip.

You can deploy your ummu from the rear or sides. You can skydive. Don't know about parachute.

J open/closes the ramp.

 

[Urwumpe]

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.

 

[gattispilot]

Like this:

what do you think of the RCS It seems sluggish.

What would be nice would be a mfd for this:
http://images3.jetphotos.net/img/1/4/2/9/32020_1217015924.jpg

the one of the compasss....

 

[Urwumpe]

Like this:

About like this, could have some blurred rotor blades as texture on it, that slowly rotate.

what do you think of the RCS It seems sluggish.

It is sluggish. you can't fly the aerobatics program of the real NH90. :lol: But them the aerodynamics are still too simplified for many helicopter maneuvers. You can't even do a hammerhead turn with this properly.

What would be nice would be a mfd for this:
http://images3.jetphotos.net/img/1/4/2/9/32020_1217015924.jpg

the one of the compasss....

A simple standard PFD? Do you want me to program one?

https://en.wikipedia.org/wiki/Primary_flight_display

---------- Post added at 08:50 PM ---------- Previous post was at 08:37 PM ----------

The latest version needs a bugfix, you expect the NH90E*.msh meshes, but there are only NH90D*.msh meshes.

 

[gattispilot]

About like this, could have some blurred rotor blades as texture on it, that slowly rotate.

Not sure about making blurred blades like this:

It is sluggish. you can't fly the aerobatics program of the real NH90. :lol: But them the aerodynamics are still too simplified for many helicopter maneuvers. You can't even do a hammerhead turn with this properly.

So increase the RCS. Might need to increase the drag to reduce forward speed?

A simple standard PFD? Do you want me to program one?

https://en.wikipedia.org/wiki/Primary_flight_display

sure

 

[Urwumpe]

Not sure about making blurred blades like this:

Use a transparent texture there, it is easier to paint and reduces the number of triangles.

So increase the RCS. Might need to increase the drag to reduce forward speed?

Increase the moments of the vertical lift function, this should work better than more drag, the vehicle isn't too fast yet, it just reacts pretty slow.

sure

OK, will look at it.

 

[gattispilot]

Use a transparent texture there, it is easier to paint and reduces the number of triangles.

Not sure how to make a transparent texture.

Increase the moments of the vertical lift function, this should work better than more drag, the vehicle isn't too fast yet, it just reacts pretty slow.

Not sure about increasing the moments

void VLiftCoeff(VESSEL *v,double aoa,double M,double Re,void *context,double *cl,double *cm,double *cd)
{
 int i;
 const int nabsc=9;
 static const double AOA[nabsc]={-180*RAD,-60*RAD,-30*RAD, -2*RAD, 15*RAD,20*RAD,25*RAD,60*RAD,180*RAD};
 static const double CL[nabsc] ={       0,      0,   -0.4,      0,    0.7,     1,   0.8,     0,      0};
 static const double CM[nabsc] ={       0,      0,  0.014, 0.0039, -0.006,-0.008,-0.010,     0,      0};
 for(i=0;i<nabsc-1 && AOA[i+1]<aoa;i++);
 double f=(aoa-AOA[i])/(AOA[i+1]-AOA[i]);
 *cl=CL[i]+(CL[i+1]-CL[i])*f;  //aoa-dependent lift coefficient
 *cm=CM[i]+(CM[i+1]-CM[i])*f;  //aoa-dependent moment coefficient
 double saoa=sin(aoa);
 double pd=0.015+0.4*saoa*saoa;  //profile drag
 *cd=pd+oapiGetInducedDrag(*cl,1.5,0.7)+oapiGetWaveDrag(M,0.75,1.0,1.1,0.04);
 //profile drag+(lift-)induced drag+transonic/supersonic wave (compressibility) drag
}

 

[Urwumpe]

CM array.

 

[gattispilot]

cm
moment coefficient. This return value defines, in which direction and how strong your vessel will rotate.

So increase this:

 static const double CM[nabsc] ={       0,      0,  0.014, 0.0039, -0.006,-0.008,-0.010,     0,      0};

Not sure what the values mean? It looks like the change is based on AOA

 

[Urwumpe]

cm
moment coefficient. This return value defines, in which direction and how strong your vessel will rotate.

So increase this:

 static const double CM[nabsc] ={       0,      0,  0.014, 0.0039, -0.006,-0.008,-0.010,     0,      0};

Not sure what the values mean? It looks like the change is based on AOA

AOA and velocity. It can be for example a force that counters the RCS when you pitch up, letting the nose drop again to zero AOA.

It could also model instabilities, when the rotation of the vessel is amplified by aerodynamics.

I think it is the better counterforce to a stronger RCS.

 

[gattispilot]

So this is what I have:

 static const double AOA[nabsc]={-180*RAD,-60*RAD,-30*RAD, -2*RAD, 15*RAD,20*RAD,25*RAD,60*RAD,180*RAD};
 static const double CL[nabsc] ={       0,      0,   -0.4,      0,    0.7,     1,   0.8,     0,      0};
 static const double CM[nabsc] ={       0,      0,  0.014, 0.0039, -0.006,-0.008,-0.010,     0,      0};

so maybe make it :

 static const double AOA[nabsc]={-180*RAD,-60*RAD,-30*RAD, -2*RAD, 15*RAD,20*RAD,25*RAD,60*RAD,180*RAD};
 static const double CL[nabsc] ={       0,      0,   -0.4,      0,    0.7,     1,   0.8,     0,      0};
 static const double CM[nabsc] ={       0,      .014,  0.028, 0.0072, -0.012,-0.016,-0.020,     0,      0};

 

[Urwumpe]

Hmm... not sure if this makes it better, would need to fly it first. I generally prefer testing it by using "Constant factor * CM" in the lift function before returning the value.