Cessna 152 1.1 Update Released!

[Cameron]

Hello, all,

This will serve as a formal forum announcement that we have released the version 1.1 update for the Cessna 152. All customers who have purchased the Cessna 152 up till now have been sent an e-mail by X-Aviation with complete installation instructions on how to update your product. Please follow these instructions carefully! For those that purchase the Cessna 152 from today forward, your purchased download will already be updated to version 1.1 for you.

There are some important fixes and requests implemented in this update.

The following is a list of additions/fixes included:

- Windscreen has been fixed.

- Turn slip has been fixed.

- Turn indicator and artificial horizon added.

- Reverse carb heat fixed.

- The airframe over stressing issue fixed.

- RPM rolling numbers replaced.

- Access ports under the wings improved.

- Nav lights fixed.

- Reversed temp gauge fixed.

- Trim wheel fixed.

As always, thanks for being a customer with X-Aviation. We appreciate your feedback and support!

Enjoy these latest updates, and stay tuned to the forum as we continually announce the latest happenings.

[woweezowee]

thanks for getting this out, I hope I can try it soon.

[boleyd]

My windshield remains dirty. If I owned a plane that would be replaced.

[steven winslow]

I updated my 152 and did a quick look around the cockpit and I have to say my windscreen still looks dirty, too.  I'll take her up for a spin later today to see if it looks better in flight.

[woweezowee]

The correction was not the dirt, but the white graphic bug one saw there (see the screenshots in the forums; I posted one of the problem and a fellow simmer, too). it is away! Never was announced that the dirt would go away - luckily, because I like it.

EDIT

Found the screenshot

[Cameron]

The correction was not the dirt, but the white graphic bug one saw there. it is away!

Markus is correct. The fix was for the gap between the panel and windscreen.

[leonell]

My altimeter shows wrong value. On my airport ( XPL data 873 ft AMSL) with QNH correctly set (value from Weather Menu) shows about 450 ft AMSL.

Other aircrafts show correct value.

Please check it.

[Airbus]

I'm looking at it now, but I cant duplicate the problem. I checked it against other aircraft also and everything seems right on my end.

[leonell]

I tested it for now on "generic" airport, LOWI and also found some interested difference between visible altimeter QNH value (29.7) and XPL internal altimeter  value (29.25).

Probably here is difference.

My version is 9.50 final (i.m. 9.50rc3), WinXP SP3 CZ,  and C152 1.1.

Hope this information and picture will help.

Added later:

I tested again, and set altimeter to visible value 29.9 (indicated as 29.74 on BARO value) and altimeter shows correctly 1893 ft (alt ftmsl and alt indicated are now same).

So problem is probably in calibration of altimeter QNH value with internal XPL value. Maybe related to 9.50, I can update to 9.55 if you want.

[woweezowee]

here is one thing i do not understand, because you said that it would change with the update: performance, rpm and the like. it feels overpowered. i just easily reached 3100 rpm, a climb out of 1000ft/min at 90ias, and cruise way over 100 ias. i have to pull back on the yoke 50 percent in order to avoid exceeding the red line. and if i do, the plane seems to be a bit too slow for the setting . but: i am not a pilot, never been in a c152 

I think it is like before the update, but shouldn't there be a change?

[alexcolka]

Hello,

My altimeter is also showing 30.00 in the Kollsman window when I reset the baro pressure to 29.92 (with a keystroke). Patch 1.1 is a great improvement. Thanks to the dev team.

Alex

[boleyd]

here is one thing i do not understand, because you said that it would change with the update: performance, rpm and the like. it feels overpowered. i just easily reached 3100 rpm, a climb out of 1000ft/min at 90ias, and cruise way over 100 ias. i have to pull back on the yoke 50 percent in order to avoid exceeding the red line. and if i do, the plane seems to be a bit too slow for the setting . but: i am not a pilot, never been in a c152 

I think it is like before the update, but shouldn't there be a change?

Level flight, 112 knots, 2900rpm altimeter 29.8, weather calm, 38fps

[Airbus]

Ill take a look at the engine operating charts again woweezowee.

And it seems as if the Baro setting is broken again ill figure out whats causing the problem.

[woweezowee]

Level flight, 112 knots, 2900rpm altimeter 29.8, weather calm, 38fps

what do you want to say?

thanks for checking, airbus. the main irritating thing is at climb out. as it is a fixed prop I would not expect it to go way beyond the red line (Jason chandlers c150 does not, just checked)

btw: baro works for me, but I use my goflight hardware to set it. 

[leonell]

Airbus: please, look at Marker Indicators too - when aircraft flyes over marker audio signal is present but no indicators are (visually) activated.

Indicators are on left side of KMA24 panel.

[boleyd]

Level flight, 112 knots, 2900rpm, altimeter 29.8, weather calm, 38fps  Should have continued that throttle at black band on the shaft of the control - cruise setting? Not sure if this is good or bad. Someone said earlier their personal 152 had similar RPM readings. However, FSX or XP planes I have seen (GA types) top out at 2500rpm. 

[leonell]

Airbus:

look at CDI (VOR indicator) too. I did try ILS approach, "localizer" needle is working fine but "glideslope" needle (GS) does not move.

In your model is red flag visible when device is receiving signal, most of CDI works reversely, flag is displayed when device does not have signal (I don't know what gauge type is in real C152).  Maybe you wittingly created gauge without GS (this can be on some VOR-only installation) but then must GS flag  show all time same value (in model GS flag is correctly changing but "glideslope" needle does not move).

[boleyd]

Cleaned my windshield.

[woweezowee]

where did you buy the sponge and cleansing material? I can't spot an FBO, shop or anything else at that local grass strip you've been to

[boleyd]

In this file:

C:\X-Plane 9\Aircraft\General Aviation\4Forces Cessna 152\objects

I blocked this file by changing its file type with some zeros:

Windowin.00000obj

It is a very crude approach and XP will give you a minor error when loading a flight. Ignore it.

I am sure there is a more elegant tactic but I prefer to use the product rather than

play programmer.

[samen]

You could just go into misc.objects in plane maker and remove that object file there. You wont get a warning after that.

[leonell]

Cleaned my windshield.

But this windshield is too much clean to be real 

[boleyd]

I am not taking an absolute position on the reality of the "clean" windshield. At the factory that is a "real" windshield but with some tint. 6 months of use later it may not be. However, if the owner of the aircraft was annoyed by a dirty windshield they might spend the money to replace it periodically. Some nutty people do nutty things. I prefer the clean windshield so I can see the countryside as clearly as possible. Fortunately, I did not have to spend any money for my "nutty" obsession for a clean windshield!  ;D 

In the other direction the person who created the XP aircraft did "spend" time making the windshield dirty thus meeting his objectives of maximum reality for an aircraft that must be old and used since they have not been made for a few years. Nothing wrong with that so long as I can find an alternative.

[steven winslow]

I actually don't mind the "dirty" windshield.  It is one of the most realistic windshields I've seen in X-Plane.  I haven't tried anything to clean it and I probably won't.  However, if I were to try something, I'd probably go into Photoshop and make some adjustments there.  Speaking of Photoshop, when can we hope for a paint kit?  Any way we can talk you out of the PSD layered files?  I've only got about an hour in this plane, but I'm liking the way she flies and I'd love to personalize her exterior.

On another note, I noticed the altimeter issue, too.  And the rpm's are quite easy to exceed redline.  I tested my Chandler 150 last night and compared it with this 152.  They both have very similar handling, but the Chandler engine stays within the redline.  Not sure which is more realistic.

[MaidenFan]

I updated the Corvalis and the 152. Either one of this will load right. They are invisible, and the Corvalis panel is screwed up. I have XPlane 9.60 RC2.