Cessna 172 Reims Rocket / Hawk XP II (freeware)

Work in progress on the plane : the 2 blade variant

No visual to show yet, so here are other updates almost ready to be delivered :

A new model option : roof windows

New light positions :

Cowl flaps and rudder trim controls :

This is amazing! I fly a C172 Hawk XP II frequently so I’m really excited for the 2-blade variant. Any chance of having a 2-blade variant without the de-rated engine? The one I fly still has the 210HP engine with the 2-blade prop (although it is listed as only being 210HP “on-climbout”, 195HP continuous HP in cruise). She’s a beauty; I plan on making a livery for it when the 2-blade prop variant is released :smiley:

Even if it is not delivered, it will be possible to include the files from the 210HP in a 2blade livery
So probably yes.
But, maybe I should give the engine choice !

This is a real Reims Rocket with real factory paint scheme!!
Any chance to do that paint scheme??Thanks in adv

WIP : the gauge cokpit is coming in slowly


State saving needs to be reworked, textures too.
A lot of testing before v3.0 is out

Thank you Bagolu for change 3.4.0 - it is awesome.
This is a dream aircraft to fly and is my “go-to” high wing GA airplane.
All radios are great and is perfect for IFR or simple VFR flying. Now if it only had deicing I could fly in any weather conditions (but I realize the original did not have deicing).

You’re right Reims Rocket flight manual says :

  • FLIGHT IN ICING CONDITIONS.
    Flight in icing conditions is strictly prohibited.

But I could add some unofficial system with a hidden control (in the book)
I’ll add that to the (long!) todolist :slight_smile:

Edit : cessna 180 flight manual has a nice “flying in icing conditions” checklist which include :

  • Open left window and scrape ice from a portion of the windshield for visibility in the landing approach.
    I’d like to implement that :slight_smile:

Thanks very much for the update. Do you also have a Garmin G5 implementation on your long to-do list by any chance? :slightly_smiling_face:

Bagolu, I have started doing a lot of night flying and what better aircraft to use than this FR172.
However I have noticed the Taxi Lights as well as the Landing Lights for sure need to be adjust to focus further away so you can see the ground. Right now the ground is as black as the night.

Thanks again for your great work.

That’s not planned at least for the Reims Rocket.
That could be an upgrade option for the C172SP G1000 maybe !

G5s in a G1000 suite? How is that going to work?
I meant as a replacement for the analog artificial horizon and gyro compass. The C172M I’m flying regularly has that. Looks like this

Ho right ! I had G5000 in mind.
I’ll check what we have as free solution for these gauges

Ok. That clears that up :slightly_smiling_face::+1:t2:
Thanks. Asobo does provide a G5. The C310 uses it IIRC.
In any case I wanted to ask why you didn’t use the Asobo gauges from the C172 or C152 for the Reims Rocket? Are they encrypted? (just curious)

I have looked quickly and haven’t found a thing in Asobo’s libraries, I’ll check again better.
I don’t have the c310 and it may be a specific gauge developped by Milviz.

  • to learn the process
  • contribute to the opensource devkit from sal1800
  • get gauges older than the ones in the 152 or 172. I could have picked in other planes with vintage gauges but it would have been a little patchwork of different things.

The current dev version has a texture rework for the gauges and panel, but I’m still not very satisfied of that. I’m still a big beginer texturer !

It’s there somewhere. The T6 ‘Undecided’ from the Reno DLC uses it as well.

Just passing on this “State Loading Error”. It has occurred about two times in the past week.

Yes, I hate that :confused: there’s a race condition at scripts start. It seems to affect a few planes. JPL152 has it too.

If something goes wrong with the instruments coded in html+js all of them fail : you can see all the screens are blank, the book too. As the code displaying HSI or Gyro is not executed, I used the warning plate, so we know this is broken.

I’m not sure this is a thing I’ve made that makes it crash : the very few times I managed to have logs, errors were in the Asobo code. But it never happened (to me) on the default planes, so that might be a library specificaly used here; usual suspect for me is the state saving library… JPL 152 does not use the state saving the same way at all, neither WBsims (we’ve spoke of that together already) but still inherit that kind of bugs.

We also experience another one were all the buttons loose there animation and seem to be unresponsive. (most of the time when reloading flight)

This bug is on my top list of things to fix, I won’t forget that, but I have not a lot of hints to solve it. Sorry about the inconvenient

Working on a new instrument…

Any plans for a bush wheeled version? Or taildragger? :kissing:

pardon my ignorance: what’s it for?