• There seems to be an uptick in Political comments in recent months. Those of us who are long time members of the site know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religious comments out of the forums.

    If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.

    Please note any post refering to a politician will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment among members. It is a poison to the community. We appreciate compliance with the rules.

    The Staff of SOH

  • Server side Maintenance is done. We still have an update to the forum software to run but that one will have to wait for a better time.

P-3 Thread continued...

Gray Eagle, I think you are correct that KBT is putting all the upgrades in one place. Looks like the p-3c_orion_v31_fsx download of 114.7MB has been replaced by a new download named OneDrive-2014-03-05.zip. This archive contains the P-3B_AEW_FSX.zip dated 3/4/2014 and the p-3c_orion_fsx_team_fs_kbt_2.zip. This should be the latest from KBT.

Just checked the download, the P-3C is dated 2/6. The latest download I have of the v3.1 is dated 2/24. Somewhat confusing as mentioned by Grey Eagle.
 
P3C Lights

When I fly the latest P3-C with lights on, I notice the the light (Circled) does not illuminate in red, rather a small tiny white light will flicker near but not centered on the light in question.

I also noted, and have a question about the light section in the Aircraft.cfg file:


[LIGHTS]
Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landing, 6=Taxi, 7=Recognition, 8=?, 9=Logo, 10=?

light.0= 9, 30.0, -0.50, -2.6, fx_Shockwave_landing_light
light.1= 9, 30.0, 0.50, -2.6, fx_Shockwave_landing_light
light.2= 7, -4.0, -25.00, 0.50, fx_Shockwave_landing_light
light.3= 7, -4.0, 25.00, 0.50, fx_Shockwave_landing_light
light.4= 4, 32.27, 0.00, 5.070, fx_vclight_p3,
//light.5= 3, -0.30, -51.60, 4.36, fx_navred, <<<< this one is /// out
//light.6= 3, -0.30, 51.60, 4.36, fx_navgre, <<<< Same-o same-o


Also, I noticed it mentioned all the Effects required for the P-3C, none were supplied in the P3C file and I have 3 of the 4 mentioned as being required.
About effects
Strobe have applied fx_storob_t38, fx_strob_t45, the fx_strob in GMAX.
These files is required .

Is fx_storob_t38 spelled correctly?


1220oew.jpg
 
When the effect of the light set up by the model is not displayed, we recommend you to set up and assign by Aircraft.cfg.

However, centering of the effect of light will be hard to be carried out for the specification of FSX.
(Also in the case of a setup in a model, it is the same)
 

Attachments

  • light.jpg
    light.jpg
    14.5 KB · Views: 1
kbt said:
When the effect of the light set up by the model is not displayed, we recommend you to set up and assign by Aircraft.cfg.

However, centering of the effect of light will be hard to be carried out for the specification of FSX.
(Also in the case of a setup in a model, it is the same)
Click to expand...

That is what I have been trying to do in the LIGHTS section of the Aircraft.cfg file. It is a bit of trial and error (hit and miss) in getting the light's to blink exactly
inside and where the lamp housings are.

I suspect that you have coded the lights in your mdl file as I do not see any coding in the LIGHTS section of the aircraft.cfg file.

I stumbled on a forum that had coded the lights for the older (V2.9) P3. When I added all of the light effects to the LIGHTS section of the aircraft.cfg file,
I noticed extra beacon lights in areas of your airplane that were not used for the current V3 P3. Some of the entries need cleaning up as some of the lights do not
align with current lights. (Close but no cigar) :adoration:

Note: I made a backup copy of the original aircraft.cfg before trying out the entries below:

[LIGHTS]
Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landing, 6=Taxi, 7=Recognition, 8=?, 9=Logo, 10=?

light.0= 9, 35.27, 0.70, -1.6, //P-3landing Nose
light.1= 9, 35.27, -0.70, -1.6, //P-3landing Nose
light.2= 7, 1.30, -24.00, -1.0, //P-3landing Wing
light.3= 7, 1.30, 24.00, -1.0, //P-3landing Wing
light.4= 7, -2.30, -24.00, -1.0, //P-3landing Wing
light.5= 7, -2.30, 24.00, -1.0, //P-3landing Wing
light.6= 4, 31.27, 0.00, 5.870, fx_vclight_p3, //VC Lighting

light.7=3, -0.2, -52.00, 4.3, fx_navredh , //Port Nav
light.8=3, -0.2, 52.00, 4.3, fx_navgreh, //Stbd Nav
light.9=2, -0.2, -52.00, 4.3, fx_strobeh, //Port Strobe
light.10=2, -0.2, 52.00, 4.3, fx_strobeh, //Stbd Strobe

light.11=1, -17.0, 0.00, -2.0, fx_beaconh , //Belly Beacon
light.12=2, -17.0, 0.00, -1.6, fx_strobeh , //Belly Strobe

light.13=1, -20.5, 0.00, 10.5, fx_beaconh , //Upper Beacon
light.14=2, -20.5, 0.00, 10.1, fx_strobeh , //Upper Strobe

light.15=3, -59.44, 0.00, 8.9, fx_navwhi , //Upper Tail Pos Light
light.16=3, -53.80, 0.00, 3.2, fx_navwhi , //Lower Tail Pos Light

light.17=7, -59.44, 0.00, 8.9, fx_recog , //Upper Tail Recgn Light
light.18=7, -53.80, 0.00, 3.2, fx_recog , //Lower Tail Recgn Light

[contact_points]

point.0=1.000, 26.18, -0.70, -7.351, 1574.803, 0.000, 2.500, 65.380, 1.2, 1.400, 0.3, 3.400, 4.800, 0.000, 0.000, 0.000
point.1=1.000, 26.18, 0.70, -7.351, 1574.803, 0.000, 2.500, 65.380, 1.2, 1.400, 0.3, 3.400, 4.800, 0.000, 0.000, 0.000
point.2=1.000, -5.917, -15.140, -7.322, 1574.803, 1.000, 3.5, 0.000, 1.0, 1.200, 1.0, 4.700, 3.500, 2.000, 0.000, 0.000
point.3=1.000, -5.917, -17.140, -7.322, 1574.803, 1.000, 3.5, 0.000, 1.0, 1.200, 1.0, 4.700, 3.500, 2.000, 0.000, 0.000
point.4=1.000, -5.917, 15.140, -7.322, 1574.803, 2.000, 3.5, 0.000, 1.0, 1.200, 1.0, 4.700, 3.500, 3.000, 0.000, 0.000
point.5=1.000, -5.917, 17.140, -7.322, 1574.803, 2.000, 3.5, 0.000, 1.0, 1.200, 1.0, 4.700, 3.500, 3.

each wheel its own contact point which as a side affect has actually made the orion sit and "haunch" as it does in real life when accelerating down the runway
smile.gif
.

Here is the reference to what you see above:

http://nzff.org/forum/index.php?showtopic=17418
 
gray eagle said:
That is what I have been trying to do in the LIGHTS section of the Aircraft.cfg file. It is a bit of trial and error (hit and miss) in getting the light's to blink exactly
inside and where the lamp housings are.

I suspect that you have coded the lights in your mdl file as I do not see any coding in the LIGHTS section of the aircraft.cfg file.

I stumbled on a forum that had coded the lights for the older (V2.9) P3. When I added all of the light effects to the LIGHTS section of the aircraft.cfg file,
I noticed extra beacon lights in areas of your airplane that were not used for the current V3 P3. Some of the entries need cleaning up as some of the lights do not
align with current lights. (Close but no cigar) :adoration:

Note: I made a backup copy of the original aircraft.cfg before trying out the entries below:

[LIGHTS]
Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landing, 6=Taxi, 7=Recognition, 8=?, 9=Logo, 10=?

light.0= 9, 35.27, 0.70, -1.6, //P-3landing Nose
light.1= 9, 35.27, -0.70, -1.6, //P-3landing Nose
light.2= 7, 1.30, -24.00, -1.0, //P-3landing Wing
light.3= 7, 1.30, 24.00, -1.0, //P-3landing Wing
light.4= 7, -2.30, -24.00, -1.0, //P-3landing Wing
light.5= 7, -2.30, 24.00, -1.0, //P-3landing Wing
light.6= 4, 31.27, 0.00, 5.870, fx_vclight_p3, //VC Lighting

light.7=3, -0.2, -52.00, 4.3, fx_navredh , //Port Nav
light.8=3, -0.2, 52.00, 4.3, fx_navgreh, //Stbd Nav
light.9=2, -0.2, -52.00, 4.3, fx_strobeh, //Port Strobe
light.10=2, -0.2, 52.00, 4.3, fx_strobeh, //Stbd Strobe

light.11=1, -17.0, 0.00, -2.0, fx_beaconh , //Belly Beacon
light.12=2, -17.0, 0.00, -1.6, fx_strobeh , //Belly Strobe

light.13=1, -20.5, 0.00, 10.5, fx_beaconh , //Upper Beacon
light.14=2, -20.5, 0.00, 10.1, fx_strobeh , //Upper Strobe

light.15=3, -59.44, 0.00, 8.9, fx_navwhi , //Upper Tail Pos Light
light.16=3, -53.80, 0.00, 3.2, fx_navwhi , //Lower Tail Pos Light

light.17=7, -59.44, 0.00, 8.9, fx_recog , //Upper Tail Recgn Light
light.18=7, -53.80, 0.00, 3.2, fx_recog , //Lower Tail Recgn Light

[contact_points]

point.0=1.000, 26.18, -0.70, -7.351, 1574.803, 0.000, 2.500, 65.380, 1.2, 1.400, 0.3, 3.400, 4.800, 0.000, 0.000, 0.000
point.1=1.000, 26.18, 0.70, -7.351, 1574.803, 0.000, 2.500, 65.380, 1.2, 1.400, 0.3, 3.400, 4.800, 0.000, 0.000, 0.000
point.2=1.000, -5.917, -15.140, -7.322, 1574.803, 1.000, 3.5, 0.000, 1.0, 1.200, 1.0, 4.700, 3.500, 2.000, 0.000, 0.000
point.3=1.000, -5.917, -17.140, -7.322, 1574.803, 1.000, 3.5, 0.000, 1.0, 1.200, 1.0, 4.700, 3.500, 2.000, 0.000, 0.000
point.4=1.000, -5.917, 15.140, -7.322, 1574.803, 2.000, 3.5, 0.000, 1.0, 1.200, 1.0, 4.700, 3.500, 3.000, 0.000, 0.000
point.5=1.000, -5.917, 17.140, -7.322, 1574.803, 2.000, 3.5, 0.000, 1.0, 1.200, 1.0, 4.700, 3.500, 3.

each wheel its own contact point which as a side affect has actually made the orion sit and "haunch" as it does in real life when accelerating down the runway
smile.gif
.

Here is the reference to what you see above:

http://nzff.org/forum/index.php?showtopic=17418
Click to expand...


note.
When you use the above temporarily, EP-3E should avoid and use it.
When it is used for EP-3E, a re-setup of a contact point is needed.
Moreover, the description of the time required of the gear animation is noted.
 
Beacon Lights fixed

kbt said:
When the effect of the light set up by the model is not displayed, we recommend you to set up and assign by Aircraft.cfg.

However, centering of the effect of light will be hard to be carried out for the specification of FSX.
(Also in the case of a setup in a model, it is the same)
Click to expand...

I tweaked the configuration settings for the upper/lower beacon (RED) lights. I spent some time adjusting the variables to where they should be positioned (trial and error) and they are
pretty close to spot on. I think there is a blinking strobe that was previously programmed into the mdl and will also blink.

attachment.php


Just add the following to the LIGHTS section of the P3-C in the aircraft.cfg file. Following two lines are numbered sequentially following the last light entry.

light.7= 1, -16.99, 0.10, -1.8, fx_beaconh , //Belly Beacon
light.8 =1, -20.78, 0.10, 10.4, fx_beaconh , //Upper Beacon
 
KBT, thanks for the update on version and fixes.

Gray-Eagle, THanks fot the beacon light fix.

Downloading the file to a new folder, and will dispose of the old one, once verified that no files in it are still needed.

Looking forward to flying this bird in it's various versions.
 
KBT, will this be uploaded somewhere once it is completed as the links you have provided always give me an error? Also, when you're done reworking this, the Orions, would you consider releasing an EA-18G with just the pylons under the wings without the ECM pods, as they sometimes fly in that configuration? With and without the centerline tank.
 
Just To Add Some Fun To The Mix

I am just finishing up the final flight plan for all four VXN-8 P3's in AI form.
I have all four of the P-3's painted on the JBAI P-3 and have got flight plans for them flying in CONUS.
They will fly from Pax at various times during the week so you may meet up with them at various NAS across the states.
The only time they are all together at Pax is on a Sunday.
I've just about finished flight plans for elsewhere in the world for all four also. These flights are represenative of where the
project birds would have flown. One flies in the Arctic, one flies around the Atlantic - S. America - Africa - Med, one flies
"down-under' and the World Traveler flies 'round the world. Should be able to upload the flight plans and paints shortly.
QUESTION FOR THE MODS: where to upload AI plans and paints on this site? Am planning to up load to Fltsim and/or Avsim
also.

The ramp at Patuxent River NAS on Sunday afternoon.
screenshot526.jpg screenshot527.jpg screenshot528.jpg

Joe
 
Sundog said:
KBT, will this be uploaded somewhere once it is completed as the links you have provided always give me an error? Also, when you're done reworking this, the Orions, would you consider releasing an EA-18G with just the pylons under the wings without the ECM pods, as they sometimes fly in that configuration? With and without the centerline tank.
Click to expand...


P-3 model of the derived type published here is due to be uploaded to SOH, Sim.com, and AVSIM with petit upgraded P-3C.
It is a rough schedule at least late in March.


About FSDS FA-18 model.
FSDS is not installed in my PC now.
Therefore, it cannot help about a FSDS model.


Although subject changes, can our data be seen from the following URL?
You may download data, when visible.
https://onedrive.live.com/?cid=a3df...#cid=A3DFC97064B66EA4&id=A3DFC97064B66EA4!188
 
Strobe lights fixed

I have also fixed the wingtip strobe lights (now visible and operational) and can be switched on/off with "L" key or the strobe light switch on the forward overhead panel

(The entries below is an accumulation of the red rotating beacon lights and the beacon lights on the port/starboard wing tips.)

If you have previously added the first two entries (#366 above) then, just copy and paste the bottom two entries to the LIGHTS section of the Aircraft.cfg file.


light.7= 1, -16.99, 0.10, -1.8, fx_beaconh , //Belly Beacon
light.8 =1, -20.78, 0.10, 10.4, fx_beaconh , //Upper Beacon
light.9=2, -0.2, -52.00, 4.3, fx_strobeh, //Port Strobe
light.10=2, -0.2, 52.00, 4.3, fx_strobeh, //Stbd Strobe
 
I was able to install this P-3C this morning and applied Gray-Eagle's light fixes.
:applause::adoration:
Took her out for a spin, and was loooovin' it
 
Just add the following to the LIGHTS section of the P3-C in the aircraft.cfg file. Following two lines are numbered sequentially following the last light entry.

light.7= 1, -16.99, 0.10, -1.8, fx_beaconh , //Belly Beacon
light.8 =1, -20.78, 0.10, 10.4, fx_beaconh , //Upper Beacon
Click to expand...

Lost the train of thought here - light 7 & 8 in your post #364 above were for the red and green nav lights. Did you intend to replace these now with these beacons?

The model actually comes with very small - very nice IMHO - red/green nav lights built in that you can only really see at dusk or night. POSKY/TDS started using these and I find them much more realistic than the usual over sized fuzzy blobs one sees in FS.
 
expat said:
Lost the train of thought here - light 7 & 8 in your post #364 above were for the red and green nav lights. Did you intend to replace these now with these beacons?

The model actually comes with very small - very nice IMHO - red/green nav lights built in that you can only really see at dusk or night. POSKY/TDS started using these and I find them much more realistic than the usual over sized fuzzy blobs one sees in FS.
Click to expand...

Train of though was

[LIGHTS]
Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landing, 6=Taxi, 7=Recognition, 8=?, 9=Logo, 10=?

light.0= 9, 30.0, -0.50, -2.6, fx_Shockwave_landing_light
light.1= 9, 30.0, 0.50, -2.6, fx_Shockwave_landing_light
light.2= 7, -4.0, -25.00, 0.50, fx_Shockwave_landing_light
light.3= 7, -4.0, 25.00, 0.50, fx_Shockwave_landing_light
light.4= 4, 32.27, 0.00, 5.070, fx_vclight_p3,
light.5= 3, -0.30, -51.60, 4.36, fx_navred,
light.6= 3, -0.30, 51.60, 4.36, fx_navgre, <<<<<<<<<<<<<<<<<<<<<<< this one was originally hashed out (////) - I unhashed them
light.7= 1, -16.99, 0.10, -1.8, fx_beaconh , //Belly Beacon <<<<<<<<<<<<<<<<<<< Ditto - I unhashed then ergo light # 8 and on.
light.8 =1, -20.78, 0.10, 10.4, fx_beaconh , //Upper Beacon <<<<<< Here on down is my additions.
light.9=2, -0.2, -52.00, 4.3, fx_strobeh, //Port Strobe
light.10=2, -0.2, 52.00, 4.3, fx_strobeh, //Stbd Strobe


All I can say shipmate is if you like em fine if you don't fantastic. Just sharing something I like and perhaps others would too. Your call. :untroubled:
 
GE
Your leadership and contribution on this project are greatly appreciated. I have taken your helpful posted lights cfg and tailored it to suit (with a few shockwave lights).
Let's keep this thread going.
expat
 
expat said:
GE
Your leadership and contribution on this project are greatly appreciated. I have taken your helpful posted lights cfg and tailored it to suit (with a few shockwave lights).
Let's keep this thread going.
expat
Click to expand...

Appreciate the kind words. I had to tweak (reposition) the coordinates a little for the upper/lower red rotating beacons. It was a lot of trial and error in setting those lights were they
would appear to blink inside the lenses. It still is a bit off depending on the angle of exterior view. I would be interested to know if you fine tuned the coordinates of the red beacons
closer to the lenses.

Thanks
:adoration:
 
Vp-90

VP-90 was a Patrol Squadron of theUS Navy Reserve squadron was established on 1 November 1970 at NAS Glenview Illinois, where it was based for the rest of its life. It was disestablished on 30 September 1994, after 25 years of service. The squadron's nickname was the Lions from 1974 onward. Elements of the squadron made 22 major overseas deployments.


Three textures included. I have modified this texture for compatibility for KBT V3 PC-3 Orion.

Available here: http://www.sim-outhouse.com/sohforums/local_links.php?catid=3&linkid=18244


wgomjk.jpg


t5jdc9.jpg


xggnwp.jpg
 
Last edited by a moderator:
Vp90 Lions

"Sorry Charlie"
j090t5.jpg


The replacement for the P-2 Neptune was the Lockheed P-3 Orion. Based on the Lockheed Electra airliner airframe, the P-3 has become the standard ASW aircraft in the world today.
This print "Sorry Charlie" depicts a P-3B Orion banking over and inspecting a Soviet 'Charlie' class submarine.


Vp-90.jpg
 
Last edited by a moderator:
Yes, it's crazy,
... it's invented completely free,
... it's completely unnecessary,

... but I love this plane .

37-CE-001_zps6dcc4ff4.jpg


Bernhard.
 
You must log in or register to reply here.
Back
Top