Hi folks,
Starting a fresh thread as requested for the newly released Northrop RF-61C Reporter. Any observations, bugs, screenshots you love or opportunities to tell us what top bananas we are for making such a lovely airplane, post 'em here. We'll be fixing anything that's found ready for the general release, and that will also ensure that things work well in the forthcoming P-61C Black Widow which will be based on the same airplane.
Cheers
I wish I had enough time to finish writing everything I sta...https://www.facebook.com/DC-Designs-2156295428024778/
Crossposting from the other thread so no one gets left out..
__________________________________________________ _
OK guys.. we made a mistake..
I'm happy that you all are enjoying our humble offering, but your not flying the whole bannana. Your manifold pressure never rises above 54 in/Hg and the WEP doesnt do anything.
This hotfix corrects that. MP should go to 63 in/Hg on mil power and 73 in/HG on WEP. This lets you achieve the full speed this aircraft is capable of. Top speed of the aircraft should rise to 450 MPH at 25000 feet in level flight. The plane should fly by the book and i guarantee your experience will be better over all..
Please download this file and replace your current FDE with it.. This is a mandatory fix.
As this is the Beta stage of development, I will be continuing to work on and improve the flight characteristics till we have them absolutely correct. I welcome any and all feedback as it really does help me see things i may have missed so that i can improve them and correct them..
I look forward to your replies..
Pam
__________________________________________________ ____________________
RF-61 reporter flight instructions addendum.
OK, before people start getting confused and angry because the plane isnt behaving as hoped I want to add this so that you all can understand and not become discouraged.
For the record:
YOU CANNOT FLY THIS PLANE LIKE ANY OTHER PLANE YOU HAVE FLOWN!
This aircraft requires that you fly it literally, by the numbers. You cannot simply increase or decrease the throttle. You MUST adjust the rpm and manifold pressure throughout each phase of your flight. That said, I am placing the correct combinations of settings below for takeoff, climbout, cruise and approach, below. You can also find these settings in Northrops P-61B Pilots Manual, though the performance of the engines in the P-61C and RF-61 are somewhat higher at the top end..
You will need to configure a joystick axis or keyboard button to control RPM. Manifold pressure is controlled through the throttle.
Enjoy.
Pam
Takeoff:
2700 rpm
63 In/Hg MP
Climbout:
2450 RPM
63 in/HG MP
Cruise:
2450 RPM
(Correction )45 in/Hg MP
Approach:
2000 RPM
30 in/Hg MP
Landing:
2000 RPM
20 in/Hg MP till short final.
Pam, I've removed the link to your update as the whole download file has been modified now.
http://www.sim-outhouse.com/sohforum...id=37&id=23602
SYSTEM :
OS:Win7 Home Premium 64 bit UAC OFF!
DX version Dx10 with Steve's Fixer.
Processor:I5 4670k overclocked to 4.4 gHz with Corsair CW-9060008-WW hydro cooler
Motherboard:Z87
RAM:16 gig 1866 gigaHz Corsair ram
Video Card:MSI 1070 8 gig ram
HD:2Tb Samsung 850 evo SSD
To err is human; to forgive is divine
Ah! Cool.. Thanks Roger..
As a suggestion to Beta Testers; if you don't have it, obtain AFSD, the small popup utility from Herve Sors. This allows you to accurately monitor everything from engine and prop parameters to accurate speed and mach values. Also testing under ISA conditions, the way to do this is via going to the "clear skies" weather theme. Aircraft performance testing values were corrected to ISA such that there was a standard to compare to.
When posting Beta test results, it will be of greatest help to Pam to post as much precise data as possible, such that she can recreate your test results. Weights, altitude, engine power settings, HP, TAS etc. Things like; "It's a dog"; "too slow" are not too helpful. Pilot notes such as for handling can be helpful, with the caveat that 10 pilots will have 10 opinions.
Cheers: Tom
Hi,
The virtual views should be adjusted to show what they are titled..?
Some are pretty far off line.
Here is the code of my adjustments which includes an observer seat view.
A starting point to be fine tuned..?
Thanks,Code:>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>. [CameraDefinition.001] Title = "Pilot View" Guid = {090ba1db-b90f-451a-ad29-781bffdb2700} Origin = Virtual Cockpit MomentumEffect = No SnapPbhAdjust = Swivel SnapPbhReturn = False PanPbhAdjust = Swivel PanPbhReturn = False Track = None ShowAxis = FALSE AllowZoom = TRUE InitialZoom = 0.50 SmoothZoomTime = 2.0 ZoomPanScalar = 1.0 ShowWeather = Yes XyzAdjust = TRUE ShowLensFlare=FALSE Category = Cockpit PitchPanRate=20 HeadingPanRate=60 InitialXyz=0.0, 0.0, -0.15 InitialPbh=5.0, 0.0, 0.0 [CameraDefinition.002] Title = "HUD View" Guid = {090ba1db-b90f-451a-ad29-781bffdb2701} Origin = Virtual Cockpit MomentumEffect = No SnapPbhAdjust = Swivel SnapPbhReturn = False PanPbhAdjust = Swivel PanPbhReturn = False Track = None ShowAxis = FALSE AllowZoom = FALSE InitialZoom = 0.70 SmoothZoomTime = 2.0 ZoomPanScalar = 1.0 ShowWeather = Yes XyzAdjust = TRUE ShowLensFlare=TRUE Category = Cockpit PitchPanRate=20 HeadingPanRate=60 InitialXyz=0, -0.00072240270674228668, 1.9871335029602051 InitialPbh=0.3240966796875, -0, 0 [CameraDefinition.003] Title = "VDI and HSD" Guid = {090ba1db-b90f-451a-ad29-781bffdb2702} Origin = Virtual Cockpit MomentumEffect = No SnapPbhAdjust = Swivel SnapPbhReturn = False PanPbhAdjust = Swivel PanPbhReturn = False Track = None ShowAxis = FALSE AllowZoom = FALSE InitialZoom = 0.40 SmoothZoomTime = 2.0 ZoomPanScalar = 1.0 ShowWeather = Yes XyzAdjust = TRUE ShowLensFlare=TRUE Category = Cockpit PitchPanRate=20 HeadingPanRate=60 InitialXyz=0.00, 0.0, 0.20 InitialPbh=38.71, -0, 0 [CameraDefinition.004] Title = "Engine Instruments" Guid = {090ba1db-b90f-451a-ad29-781bffdb2703} Origin = Virtual Cockpit MomentumEffect = No SnapPbhAdjust = Swivel SnapPbhReturn = False PanPbhAdjust = Swivel PanPbhReturn = False Track = None ShowAxis = FALSE AllowZoom = FALSE InitialZoom = 0.50 SmoothZoomTime = 2.0 ZoomPanScalar = 1.0 ShowWeather = Yes XyzAdjust = TRUE ShowLensFlare=TRUE Category = Cockpit PitchPanRate=20 HeadingPanRate=60 InitialXyz=0.00, 0.0, 0.00 InitialPbh=30.00, -0, 347 [CameraDefinition.005] Title = "Left Console" Guid = {090ba1db-b90f-451a-ad29-781bffdb2704} Origin = Virtual Cockpit MomentumEffect = No SnapPbhAdjust = Swivel SnapPbhReturn = False PanPbhAdjust = Swivel PanPbhReturn = False Track = None ShowAxis = FALSE AllowZoom = FALSE InitialZoom = 0.40 SmoothZoomTime = 2.0 ZoomPanScalar = 1.0 ShowWeather = Yes XyzAdjust = TRUE ShowLensFlare=TRUE Category = Cockpit PitchPanRate=20 HeadingPanRate=60 InitialXyz=0.00, 0.0, 0.30 InitialPbh=52.00, -0, 300 [CameraDefinition.006] Title = "Display Controls Console" Guid = {090ba1db-b90f-451a-ad29-781bffdb2706} Origin = Virtual Cockpit MomentumEffect = No SnapPbhAdjust = Swivel SnapPbhReturn = False PanPbhAdjust = Swivel PanPbhReturn = False Track = None ShowAxis = FALSE AllowZoom = FALSE InitialZoom = 0.30 SmoothZoomTime = 2.0 ZoomPanScalar = 1.0 ShowWeather = Yes XyzAdjust = TRUE ShowLensFlare=TRUE Category = Cockpit PitchPanRate=20 HeadingPanRate=60 InitialXyz=0.25089737772941589, -0.35782033205032349, 0.20013436675071716 InitialPbh=34.91455078125, 0, 5.218505859375 [CameraDefinition.007] Title = "Right Console" Guid = {090ba1db-b90f-451a-ad29-781bffdb2707} Origin = Virtual Cockpit MomentumEffect = No SnapPbhAdjust = Swivel SnapPbhReturn = False PanPbhAdjust = Swivel PanPbhReturn = False Track = None ShowAxis = FALSE AllowZoom = FALSE InitialZoom = 0.70 SmoothZoomTime = 2.0 ZoomPanScalar = 1.0 ShowWeather = Yes XyzAdjust = TRUE ShowLensFlare=TRUE Category = Cockpit PitchPanRate=20 HeadingPanRate=60 InitialXyz=0.00, 0.0, 0.10 InitialPbh=46.00, -0, 65 [CameraDefinition.008] Title = "Observer Seat" Guid = {090ba1db-b90f-451a-ad29-781bffdb2742} Origin = Virtual Cockpit MomentumEffect = No SnapPbhAdjust = Swivel SnapPbhReturn = False PanPbhAdjust = Swivel PanPbhReturn = False Track = None ShowAxis = FALSE AllowZoom = FALSE InitialZoom = 0.50 SmoothZoomTime = 2.0 ZoomPanScalar = 1.0 ShowWeather = Yes XyzAdjust = TRUE ShowLensFlare=TRUE Category = Cockpit PitchPanRate=20 HeadingPanRate=60 InitialXyz=0.0, 0.15, -1.70 InitialPbh=7.0, 0.0, 0.0 [CameraDefinition.009] Title = "Looking Aft" Guid = {090ba1db-b90f-451a-ad29-781bffdb2705} Origin = Virtual Cockpit MomentumEffect = No SnapPbhAdjust = Swivel SnapPbhReturn = False PanPbhAdjust = Swivel PanPbhReturn = False Track = None ShowAxis = FALSE AllowZoom = FALSE InitialZoom = 0.30 SmoothZoomTime = 2.0 ZoomPanScalar = 1.0 ShowWeather = Yes XyzAdjust = TRUE ShowLensFlare=TRUE Category = Cockpit PitchPanRate=20 HeadingPanRate=60 InitialXyz=0.0, 0.4, -2.30 InitialPbh=7.0, 0.0, 180.0
Tony
Damn Tony.. Thank you. I'm really horrible with camera's and really appreciate your doing this..Originally Posted by Seahawk72s
Pam
Thankds Tom.. I appreciate your posting this.. It certainly will help immensely. I also consider pireps important even if the pilots all have different opinionss, because there will always be a thread of truth running through them which also helps me pinpoint values. If youve never seen AFSD ( Advanced Flight Sim Data) heres what it looks like overlayed on top of the cockpit..
Some switches go in reverse direction to on\off positions. (Up =ON, Down=Off..?)
Light 2 looks a little big, something smaller for a fixed beacon.
Light 2 looks like a beacon, maybe add a beacon switch to control it.
I'd say maybe keep the strobe switch for possible use..?
Lights 0, 1, 2, need to be un-remed to operate.
Lights 0, 1, 2, need to be re-positioned.
Cockpit light switch moves Nav switch in unison.Code:light.0 = 3, -19.60, 33.00, 3.45, fx_navgre light.1 = 3, -19.85, -32.90, 3.46, fx_navred light.2 = 1, -24.863, 0, -2.900,fx_shockwave_beaconh // fx_lightObsRedSteady
Taxi switch doesn't work.
No Landing light switch on side console.
Not sure what test switch does.
In VC panel\cockpit light switch has little effect. Gauges can't be read at night.
Do the landing light effects want to be moved back toward the source a bit..?
At least a little further out to position in front of the lenses..
Does a taxi light effect want to be added..?Code:light.5 = 5, -20.80, -23.30, 1.50, fx_Shockwave_landing_light // Shockwave light light.6 = 5, -20.80, 23.30, 1.50, fx_Shockwave_landing_light // Shockwave light
Recognition lights..?Code:light.7 =6, -7.20, -0.30, -2.85, fx_shockwave_landing_light_747_lw,
If you are into strobes.Code:light.8 = 7, -33.500, 9.50, -1.030, fx_navred // bottom red fuselage recognition light.9 = 7, -34.500, 9.50, -0.970, fx_navwhi // bottom amber fuselage recognition light.10 = 7, -35.500, 9.50, -0.970, fx_navgre // bottom green fuselage recognition
Code:light.11 =2, -19.60, 33.00, 3.45, fx_strobeh , light.12 =2, -19.85, -32.90, 3.46, fx_strobeh ,
I realize some of this is open to interpetation and the need to move switches and see lights blink.
Ahhh, the Lights.. Afraid i didnt address the lights till last night. Mia Culpa. Please accept my apology's. Here is what it should be..
][lights]
//Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landing
light.0 = 3, -20.83, 28.539, 3.171, fx_navgre
light.1 = 3, -20.83, -28.539, 3.171, fx_navred
//light.2 = 2, -24.863, 0, -3.303, fx_lightObsRedSteady
light.3 = 4, -10.109, 0, 1.645, fx_vclight_deepred.fx
light.4 = 4, -15.92, 0, 3.78, fx_vclight_deepred.fx
light.5 = 5, -21.92, -23.20, 1.8, fx_landing.fx
light.6 = 5, -21.92, 23.20, 1.8, fx_landing.fx
OK, For nyone applying the hofix. PLEASE delete your existing aircraft.cfg and air file, before copying in the new files. Thi will eliminate potential problems with file privileges..
Thanks.
sleepy Pam
off to bed..
Got some more feedback for ya'
I see that Seahawk noted the issue with the lights. Only two things I can add is that after startup the lower white center nav light is on automatically and if you use a shortcut key of Ctrl-L both nav and landing lights were on simultaneously. Ctrl-L should have been for landing lights only.
Once airborne I was getting a vortex for the right wing only. None on the left, and I wasn't sure if I should see any at low altitude.
And speaking of switches, the battery switch seems inop. Battery is on regardless of switch position.
BTW. Thanks for the updated interior views, Skyhawk.
That's all for now. Back to the skies.
-- WH
If at first you don't succeed, try, try,try again. ... or go read the manual.
I took a short flight today.
The WAY it flies is great. Very stable, but responsive. A joy to fly!
A couple little details I noticed in the VC:
The Cowl Flaps gauge doesn't work. No matter where the switches are positioned, or the KB commands used, the gauge needles never move from all the way down.
As to the RPM gauge: No matter where I position the Prop Levers on the throttle quadrant, OR use the KB commands, it's as though they are full RPM all the time. If I try to lower the RPM of the props at 25,000' MSL, speed seems irrelevant, MP at the recommended cruise setting of 45 In., the gauge needles remain in the center of the red arc, and there comes a point at which the gauge suddenly climbs up to the top of the scale and stays there. Only way to DECREASE the reading is to INCREASE the prop setting to the max again. I was trying to match the settings in your post above, buuuut...
Am I doing something wrong there? Am I reading the wrong gauge? It IS labeled RPM, and is the only one I can see. Wouldn't be the first time I messed something up.
More to come as I can fly 'er...
Pat☺
Fly Free, always!
Sgt of Marines
USMC, 10 years proud service.
Inactive now...
I modified my panel with my panel editor. I repositioned the manifold gauge to be beside the rpm gauge so there both easier to read at a glance. Since there where two carb heat gauges I removed one on main panel and replaced it with an oil quantity gauge. There wasn't a cowl flap gauge installed on the original panel so I installed one along with a fuel flow gauge where there was a clock installed. I also replaced the smaller altimeter gauge with an adf gauge. For the dive brakes I installed an indicator light on main panel. Try this and see how you like it. Back up your original panel just in case you don't. Attachment enclosed. Robert
Ok, I was able to take another short flight tonight.
I used Robert's updated panel. It was very nice having the changes he made, like the Cowl Flaps gauge, and having the Manifold pressure right next to the RPM gauge. Realistic to the actual aircraft? I have no idea, but it was much easier to fly that way. I was able to keep the flight instruments AND the critical engine instruments in sight all at the same time.
If this new panel hadn't appeared, I was going to make a pop-up with the MP and the RPM gauges in it, so I could do the same. IE: Keep in sight what I need to.
I AM going to add a GPS pop-up.
I discovered that the pilot seems to "loose control" of the prop RPM at about 13,000' MSL as I had mentioned in my last post. The RPM climbed up into the red arc, and stayed there. If the pilot (me), lowered the RPM controls, either with the levers or the KB commands, sufficiently, the gauge would suddenly climb up and peg at it's maximum value. At least until the Prop controls were raised again, in which case it returned to the red arc on the gauge. And stayed there, no matter what.
I was reading through the Propeller section of the aircraft.cfg file, and I DID notice the line low_speed_theory_limit=160.00000 . I am no propeller expert, but every other entry I've seen has been 80, not 160. I wonder if this is what's causing the strange behaviour I am seeing. Just a thought. I will try it tomorrow and see what happens.
In the same section: Did the plane have counter-rotating props? If so, the line rotation = 1,1 should read -1, 1. I haven't checked, but I've seen other posts that say the props rotate the wrong way, or backwards. If so, and they both rotate the same way, changing the line to -1, -1 will reverse their direction.
I don't know if any of this is relevant or not I am NOT an FDE dev, but maybe...
Pat☺
Sgt of Marines
USMC, 10 years proud service.
Inactive now...
Thank all of you for your observations on the flight model. They will become the main bullet items during my testing, and I'll do my best to fix them..
High RPM: confirmed. I dont know if its natural or not as Ive forgotten a lott of things over the years, however, as long as the manifold pressure is high, That engine is sucking in gas and will continue to run at that rpm supported by that manifold pressure. Once the manifold pressure is reduced, you can adjust the rpm. I'm currently looking deeper into this.. the other way to lower rpm, is coarsen your prop pitch. The coarser the pitch, the more drag it puts on the shaft and the more power it takes to maintain that rpm.
RPM climbing into the red above 13000 MSL: IF i cant duplicate this, you and I will work together along with anyone else that may be having this issue to solve it and get you up and flying right.. Please download the "Advanced Flight Sim Data " application as we'll need that to disect the problem.. Thanks..
Low_speed_theory_limit: this is a value in feet per second at which the low speed theory becomes blended into the flight model. a value of 80, means it doesnt kick in till your only doing 80 feet per second. My good sir, you can almost run that fast. the absolute slowest this plane can fly, with full flaps and extreme nose up position, is 80Mph, which equates to 117.333 feet per second. 160 feet per second equates out to somewhere around 110 mph. This plane can take off at 110 but mostly it lands at 110 and your losing altitude while doing so. it's very slow
One of the phenomena i've seen with this plane is that any adjustment to rpm, manifold pressure, throttles or what not, has a delayed reaction. Those props are almost 13 feet across and weight over a thousand pounds each. They remind me of the old axiom that sometimes, the tail wags the dog. They dont want to slow down and they dont want to speed up either.. So everything you chnge, will take time. it's making getting setting documented a real pain because I set 40 In/HG and 2450 RPM as cruising speed, but first you have to lower the manifold pressure so it stops guzzling gas and slows down enough to change the rpm, then you have to change the rpm to 2450, then raise the manifold pressure to 45, and it STILL is wrong and only takes you to 300 mph.. Please bear with me.. If you pull back on the throttles, it may take up too a minute and a half for the plane to slow down.. it's just got that little drag, and that much power. Northrop built hotrods, that scared the bejeezuz out of the pentagon. The Pentagon demanded they put speed brakes on the P-61C because they were afraid it would overshoot its targets it was so fast ( not to mention heavy at 34000 pounds ). This plane is faster, and lessons learned, has smaller speed brakes that wont rip the wings off..
Fixes in place today and results:
The plane was developing over 4000 shaft RPM at 2500 feet, driving it to over 500 mph. That has been fixed.
Fixing the above cause the plane to not be able to reach cruise speed at low altitudes. That has been fixed.
Fixing the cruise speed problem caused the plane to not want to start. Almost fixed but you have to give it gas..
And thats where i sit at the moment
Yup, thanks for all the testing and observations folks! Pam sounds like she's well on top of the engine issues, and although there are numerous modelling bugs they're all fortunately very easy to fix.
Regarding the cowl flap gauges: I am not yet at the stage where I can develop my own. I did build a custom airspeed indicator for the Reporter, but that was a bit simpler. As the airplane can be used in either FSX or P3D, I didn't want to alias a gauge that would work in one sim and not the other. Therefore, I decided to leave it to the user to pop a gauge in there if they want to. If you have altered the panel yourself and it works in either sim, then please feel free to distribute the revised panel to the wider community as an add-on once we release the official v1
P.S. The port wingtip vapour trail is an artifact in the engine smoke gauge which shouldn't be there, it's being fixed.
no vapor trails here:
Great project guys. Not had a lot of time to use it yet but very impressive in all respects. Thanks.
Matt
Thanks to all involved in this project. Great plane. So far all I can report is the canopy opens then closes again on SHIFT-E. From inside the VC there is an animation of the canopy sliding back, along with the sound. But then it shows closed again. From spot view there was no canopy sliding back animation. Multiple applications of SHIFT-E always results in the "MAIN EXIT OPENING" red text. Never closing. I'm not calling for emergency services. They'll want to bash it with an ax...
EDIT: Went on another flight and the canopy worked fine. If I can duplicate it again I will note the conditions.
MB: GIGABYTE GA-X299 UD4 PRO ATX
CPU: Intel(R) Core™ Processor i9-10900X Ten-Core 3.7GHz
MEM: 64GB (8GBx8) DDR4/3000MHz Quad Channel
GPU: RTX 3080 Ti 12GB GDDR6
OS: Win 10 Pro 64bit
HP Reverb G2
This is a great model and understandably still a work in progress.
I'm wondering if you could leave in place a few open vcockpit surfaces so those of us who are
panel geeks can place gauges we may like to see. The ones that I can think of are the observers
panel, the little O2 panel by the pilot, the limit lights panel and the lights box..?
Of course I have no idea what you have planned for the future so what I have wrote may be complete garbage.
A lot of folks have been waiting for this plane, maybe we can help out a little bit.
(panel graphics are Lobo Da Silva, gauges by Milton and others)
Something that I have always wanted developers to do, but few will, is to provide a model that has flat panel spaces so the user can place their desired gauges, radios, and avionics. I'm a modern day flight simmer, so I like having a GPS, modern radios, maybe weather radar, and a place for beacon and strobe switches in the virtual cockpit. That is one reason why I so enjoy Milton Shupe's D18S and A-26 Invader.
My computer: ABS Gladiator Gaming PC featuring an Intel 10700F CPU, EVGA CLC-240 AIO cooler (dead fans replaced with Noctua fans), Asus Tuf Gaming B460M Plus motherboard, 16GB DDR4-3000 RAM, 1 TB NVMe SSD, EVGA RTX3070 FTW3 video card, dead EVGA 750 watt power supply replaced with Antec 900 watt PSU.
Pam,
Thank you for that explanation of the low speed theory blending setting! That is THE first explanation I've seen of it that makes sense to my little pea brain.
I wonder why no other developer I've seen changes it from 80. I can't believe no other go fast plane can go slow enough that 80 is appropriate. By the same token, I am FAR from a person with thousands of aircraft. Maybe I'm just missing it when the developers DO change it.
Then again, that wondering applies to a lot of default settings in the aircraft.cfg file I see as I go.
Thanks again!
I've DL'd and installed AFSD should it become necessary. I will also take your advice on changing the prop RPM. Like I say, I'm probably doing something wrong. We shall soon see what we shall soon see, si?
More to come later, after I get some stick time on this fantastic plane.
Pat☺
Sgt of Marines
USMC, 10 years proud service.
Inactive now...
For the vapour trail I simply disabled the top line in the smoke section. The other pair still appear when pulling Gs. I'm gonna try the updated file now.Yup, thanks for all the testing and observations folks! Pam sounds like she's well on top of the engine issues, and although there are numerous modelling bugs they're all fortunately very easy to fix.
Regarding the cowl flap gauges: I am not yet at the stage where I can develop my own. I did build a custom airspeed indicator for the Reporter, but that was a bit simpler. As the airplane can be used in either FSX or P3D, I didn't want to alias a gauge that would work in one sim and not the other. Therefore, I decided to leave it to the user to pop a gauge in there if they want to. If you have altered the panel yourself and it works in either sim, then please feel free to distribute the revised panel to the wider community as an add-on once we release the official v1
P.S. The port wingtip vapour trail is an artifact in the engine smoke gauge which shouldn't be there, it's being fixed.
Running on P3D 4.2 here, and it's a great flyer!
I bumped into the prop speed issue as well, but it was when crossing FL400.
They went all the way to the far end of the dial and from then on, setting them to full fine was the only way to get them back into the red zone until landing. The rest of the handling feels excellent and the stability on approach is awesome.
The plane is apparently capable of exceeding it's critical mach number in level flight and even in a slight climb at those altitudes with full throttle applied.
No other strangeness was encountered and the ceiling seems to be 54-55k (estimated, I stopped around 54.5k) where handling is...as expected in very thin air but perfectly controllable nevertheless..
Other notes:
The skins are pretty awesome and screaming for bump maps! (do the masters exist in 4096?)
The aluminum probably needs to be a bit clearer/whiter? Just going from the available pictures.
Quite amazing work on an airframe I always found fascinating. My thanks as well!
Members who have read this thread: 0
Posting Permissions
FSX
Reply With Quote
Bookmarks