Jump to content

Recommended Posts

Cheers guys

CounterNodeFormat=counter_alt%d

I assume counter should be name of the mesh I have ?

Edited by russouk2004

Share this post


Link to post
Share on other sites

yes

and

for example 4 dig counter in cokcpit ini.

[RadarAltimeter]
Type=RADAR_ALTIMETER
CounterNodeFormat=RADalt_dig%d
MovementType=ANALOG_COUNTER
ValueUnit=FEET

 

represent those 4 nodes linked to one parent mesh.

                Altimeter_box [144 polys, 160 verts] '03'
                    RADalt_dig1 [20 polys, 40 verts] '21b- Default'
                    RADalt_dig2 [20 polys, 40 verts] '21b- Default'
                    RADalt_dig3 [20 polys, 40 verts] '21b- Default'
                    RADalt_dig4 [20 polys, 40 verts] '21b- Default'

important is meshes should have names ended by dig1, dig2 dig3, dig4

last number on counter is dig1 where a higher dig(4/5/6) is the first number on the counter

 

samp.thumb.jpg.33c282fe9eb53999d4eb893cb700fa9a.jpg

 

 

  • Thanks 1

Share this post


Link to post
Share on other sites

Pilot and co refuses to budge...they are not part of cockpit lod but added to the c47 the normal way...only way I know is to remove them from the a\c or move cockpit so far forwards they cant be seen ?

also the counter refuses to move no matter what...Im sure im overlooking summat...atm its linked to the gauge.

any idea warmly welcomed...driving me nuts now lol...ironed out all other probs...just these two things annoying me lol...heres info on the counter.as is  btw (reset the meshes so they are all correct size and all pivot aligned to world\local)

mesh name...   P_Alt_dig1

parent altimeter gauge.

rotation is to world or local Rotation_X 

based gauge settings from the c47 pit

I tried the settings recomended but nothing...what logan and yak suggested....weird ..when things go wrong for me the go wrong lol

Image3.jpg

Edited by russouk2004

Share this post


Link to post
Share on other sites

The method I suggested for hiding the pilot is for the AC.lod not for the cockpit.lod so have to add it to the AC_data.ini, only thing you have to make sure, that the pilot(s) is/are linked to the interior of the pit on the AC model, then it will make it go away.

After work will make some tests as one of my coming pits will have a similar altimeter, just not that far in to it.

Share this post


Link to post
Share on other sites

have you trined "opencockpit=true", and "Moved" things in the cockpit ini???

Share this post


Link to post
Share on other sites

I am lost ..

those are just normal pilots from a pilot folder? the maybe create new aircraft component in data ini 

 

[AircraftData]
EmptyMass=10900.0
EmptyInertia=197413.39,30260.70,203674.09
ReferenceArea=38.00
ReferenceSpan=11.10
ReferenceChord=3.71
ReferenceLength=17.32
CGPosition=0.00,-1.20,0.15
UseMetricUnit=TRUE 
Component[001]=Fuselage
Component[002]=Nose
Component[003]=LeftWing
Component[004]=RightWing
Component[005]=LeftStab
Component[006]=RightStab
Component[007]=LeftVertTail
Component[008]=RightVertTail
Component[009]=LeftOuterWing
Component[010]=RightOuterWing

Component[011]=placeforpilots

then that component...

 

[placefor pilots]
ModelNodeName=
ShowFromCockpit=FALSE
MassFraction=
HasAeroCoefficients=FALSE
CLa=0

DamageRating=DISABLED
SystemName[001]=pilot
SystemName[002]=copilot

 

 

Share this post


Link to post
Share on other sites

Thanks yak and logan

removes them from cockpit view fine....but adding the placeforpilots method makes no pilots in the a\c outside view...will just move pit forwards...only thing works.

its stock c-47 using...

ok using c47 settings and a little moving...seems fine now....offset seemed to do it..

still getting oddities with this counter tried as new altimeter

 

[Altimeter2]
Type=PRESSURE_ALTIMETER
NodeName=P_alt_dig1
CounterNodeFormat=alt_dig%d
MovementType=ROTATION_X
ValueUnit=FEET
Set[01].Position=0.0
Set[01].Value=0.0
Set[02].Position=-360.0
Set[02].Value=10000.0

 

and

[Altimeter2]
Type=PRESSURE_ALTIMETER_1
NodeName=P_alt_dig1
MovementType=ROTATION_X
ValueUnit=FEET
Set[01].Position=0.0
Set[01].Value=0.0
Set[02].Position=-360.0
Set[02].Value=10000.0

 

but it insists on counting 1000s of feet not 10k will keep trying

 

img00046.JPG

img00047.JPG

Edited by russouk2004
  • Like 1

Share this post


Link to post
Share on other sites

I did some testing, there is one thing that you need to do with the name of the mesh.

In the cockpit.ini the bellow is enough, not need other stuff

[Altcounter10K]
Type=PRESSURE_ALTIMETER
CounterNodeFormat=Alt_dig%d <---- for you P_alt_dig%d
MovementType=ANALOG_COUNTER
ValueUnit=FEET

Now the naming:  "P_alt_dig4" is for thousands of feets and "P_alt_dig5" would show 10k increments

In the test I had mine named Alt_dig4 so I can see thousands of meters and works OK. If you use for example _dig4 and use the Scale=0.1 then would show 10k also, but I think _dig5 would work just fine.

 

 

counter.jpg

Edited by logan4
  • Like 1

Share this post


Link to post
Share on other sites

cheers logan...been digging around archives and found the old thread giving lists of entries too...ur a gent ty man

  • Thanks 1

Share this post


Link to post
Share on other sites

wtf now it spins around as if its counting feet per second lol...its exactly same as the c47 A pit kesselbrut made but my counter refuses to work at all correctly  w t ffffffff  lol

tried few ways....also when tried this way suggested it read 1200 ft and the counter was at 5 even though at 10ft above sea level....then soon as left ground spun like a looney...its exactly as c47 cockpit even pivots are same as are names now but will not count 10k feet  it just stays at 0 when I use the same entry as the c47 pit kess made  

Instrument[011]=Altimeter100
Instrument[012]=Altimeter1000
Instrument[013]=Altimeter10KP

 

[Altimeter100]
Type=PRESSURE_ALTIMETER_2
NodeName=ALT_100_NDL
MovementType=ROTATION_Y
ValueUnit=FEET
Set[01].Position=0.0
Set[01].Value=0.0
Set[02].Position=360.0
Set[02].Value=1000.0

[Altimeter1000]
Type=PRESSURE_ALTIMETER_2
NodeName=ALT_1000_NDL
MovementType=ROTATION_Y
ValueUnit=FEET
Set[01].Position=0.0
Set[01].Value=0.0
Set[02].Position=360.0
Set[02].Value=10000.0

[Altimeter10KP]
Type=PRESSURE_ALTIMETER  also tried  PRESSURE_ALTIMETER_2
CounterNodeFormat=alt_dig%d
MovementType=ANALOG_COUNTER
ValueUnit=FEET
//Set[01].Position=0.0
//Set[01].Value=0.0
//Set[02].Position=-360.0
//Set[02].Value=10000.0

 

[Altimeter10KP]
Type=PRESSURE_ALTIMETER_2
CounterNodeFormat=alt_dig%d
MovementType=ANALOG_COUNTER
ValueUnit=FEET
Set[01].Position=0.0
Set[01].Value=0.0
Set[02].Position=-360.0
Set[02].Value=10000.0

 

 

Image2.jpg

Edited by russouk2004

Share this post


Link to post
Share on other sites

All working now big thanks to helpers especially Logan   cheers guys

  • Like 1
  • Thanks 1

Share this post


Link to post
Share on other sites

Congrats Russ, know it was a long haul.  And you're absolutely right - Logan's brain power on these kind of challenges is a God Send!

  • Like 1

Share this post


Link to post
Share on other sites

you too mate for some help too....now just add co-pilot and done...got one somewhere that should look the biz..

just need now a dedicated Dc-3  :pilotfly:

Edited by russouk2004
  • Like 1
  • Thanks 1

Share this post


Link to post
Share on other sites

yeah, cause the entry doors are markedly different from the C-47/53 than the civie version (I should know, there's one on a pole 1/2 mile west of me at Santa Monica Airport! -Donald Douglas' personal bird!)

Share this post


Link to post
Share on other sites

A companion....yoke was proving a bore as it went through the clipboard...but it seems in the DC series you ould lock the yoke,so I have limited its movement for copilot version...will have pilot...and one with co pilot...looking at pic...might put left hand on the levers(red) and other holding clipboard up a bit higher so it misses the yoke.

btw this is from Freeware FSX Dc-3 HCAA model...most of it I remade anyways...all gauges buttons lights.panel ..some of the other parts etc...its about 40% rebuilt

img00055.JPG

img00056.JPG

Edited by russouk2004
  • Like 5

Share this post


Link to post
Share on other sites

so, we're getting a new replacement cockpit for C-47? To replace Kesselbruts, yes?

It's really looking good!

Share this post


Link to post
Share on other sites

asap....just few bits to edit....like the co pilot position of arms....pit has a few different colour textures too..will post screens later.as they need some additions..I will convert the freeware DC-3 t a later date as ive but a much to do...like the static H-19...gimme day or two and I ll send it to you kev...pit should be ready sunday

image.thumb.png.efdc0e1992812a085762ad145b273bfb.png

Edited by russouk2004
  • Like 2

Share this post


Link to post
Share on other sites

Russ, looking good.  One suggestion though, it might just be the screenshot perspective,...some of the cockpit accessories esp. the switches look like they're out of scale (too big in my opinion).  Not sure if that's the case but something to consider, it's nice to have this included and love the Pilot model

Share this post


Link to post
Share on other sites

yeah its the screenshot I think,I did them to scale of the model.  what you reckon

ty btw

Image2.jpg

Edited by russouk2004
  • Like 2

Share this post


Link to post
Share on other sites

SWEEEETT!!!!!!!!

Share this post


Link to post
Share on other sites

Hi there,

Thanks a lot for your post. How do I turn on the external fuel tank light indicator in the cockpit for F-4Es Phantom? Thank you.

Share this post


Link to post
Share on other sites

if its not set to work in 3d model you cant.....check it in mues lod viewer to see if it has a texture for on\off...if so an ini edit will get it to work.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×

Important Information

By using this site, you agree to our Terms of Use, Privacy Policy, and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..