Cessna 182 T Skylane model

HHS81 commented 6 years ago

This is more a memo and checklist for myself creating the Cessna 182 T Garmin 1000 model 2004-2010.

Config:

[ ] c182-base-set.xml + c182s-set.xml and c182t-set.xml
[x] keep Models/c182s.xml
[x] add Models/c182t.xml
[x] rename Models/interior-model.xml to Models/c182s-interior-model.xml
[x] add Models/c182t-interior-model.xml
[ ] add and seperate livery-folder like I did on the Dornier 328
[x] splash screens and preview images
[x] add failures from the C182S
[ ] add cabin temp

Exterior:

[ ] air intake design change
[ ] strake on the fin
[ ] wheel fairings new design
[ ] cut out housing for new navlight location on wings
[ ] make at least two Cessna 182 T example liveries

Interior:

Panel:

[ ] model the new panel, seperated panel object for breakers/switch panel due to lightmap
[ ] uvmap them on at least 1024x2048px, (or mabye better 2048x2048px), keeping the lower part of the panel
[ ] uvmap the glareshield better, especially the loudspeaker(?)/ vent grill(?)
[ ] new textures of the panel (Gilberto?)
[ ] new lightmaps - no glareshield lights needed

Seats:

[ ] model new seats
[ ] uvmap new seats
[ ] new textures - new colors (Gilberto?)

Cabin walls and ceiling

[ ] model new ceiling, incooperate possible oxygen panel if possible
[ ] air vent moving to its new location on the A-Frame
[ ] new textures - brighter colors
[ ] sun visor is now also able to be rotated to the side.

Electrical System:

[x] new electrical system just for c182t regarding Garmin 1000 and second battery (see #355)

FDM:

[ ] add c182t.xml as new fdm with adjusted fdm for higher speed at higher altitudes (check prop type before)

gilbertohasnofb commented 6 years ago

Really looking forward to this one!

hbeni commented 6 years ago

Mee too!

wlbragg commented 6 years ago

Yep, I'm on board!

MatLys commented 5 years ago

I am so on board for this. We need to make all the use we can out of the C172, it's just too good to not be overhauled.

hbeni commented 5 years ago

@stuartbuchanan I have created a new branch called C182T, merged and synchronized your files manually. Unless I forgot something, the branch C182T is uptodate, and all errors removed. So you can work from this branch on. Please @stuartbuchanan @hbeni @gilbertohasnofb check if everything is correct, then I will merge the the branch into master. I think #258 will give us a roadmap.

Are we aiming for this cockpit layout? https://www.youtube.com/watch?v=rlrEUt9oMvY ?

What i found in the C182T branch:

Splash screen and Launcher image still c182s
failures: they seem not to be initialized (failures nasal file not called from set file? only default ones work, like ADF)
The default-factory transponder code in aircraft options is not set initially (maybe we should hide this if not applicable?)
Cabin Temp tooltips are not up to date (missing change indicator)
Performance is an issue at my machine, it gets nearly unplayable at 4x

stuartbuchanan commented 5 years ago

Hi Benedikt,

I've not yet implemented the transponder in the FG1000, which is why it's not set. (The UI is a real pain for this with various timers)

In terms of cockpit layout, the video is pretty close, though I can't see the bottom of the panel. However, in the medium term I want to replace the KAP140 autopilot with the Garmin GFC700. That should be fairly straightforward, though I need to check if the 182 autopilot configuration include PIDs for NAV etc.

Yes, performance is an issue. What do you mean by "4x"?

-Stuart

On Mon, Jan 7, 2019 at 6:07 PM Benedikt Hallinger notifications@github.com wrote:

@stuartbuchanan https://github.com/stuartbuchanan I have created a new branch called C182T, merged and synchronized your files manually. Unless I forgot something, the branch C182T is uptodate, and all errors removed. So you can work from this branch on. Please @stuartbuchanan https://github.com/stuartbuchanan @hbeni https://github.com/hbeni @gilbertohasnofb https://github.com/gilbertohasnofb check if everything is correct, then I will merge the the branch into master. I think #258 https://github.com/HHS81/c182s/issues/258 will give us a roadmap.

Are we aiming for this cockpit layout? https://www.youtube.com/watch?v=rlrEUt9oMvY ?

What i found in the C182T branch:

Splash screen and Launcher image still c182s

failures: they seem not to be initialized (failures nasal file not called from set file? only default ones work, like ADF)

The default-factory transponder code in aircraft options is not set initially (maybe we should hide this if not applicable?)

Cabin Temp tooltips are not up to date (missing change indicator)

Performance is an issue at my machine, it gets nearly unplayable at 4x

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/HHS81/c182s/issues/258#issuecomment-452026350, or mute the thread https://github.com/notifications/unsubscribe-auth/AL4umNuknPhp7r_Jx6aWvF8CxLFvtMFaks5vA4zFgaJpZM4SBc9B .

hbeni commented 5 years ago

By 4x i meant time acceleration. With 1x it runs OK here (tough not perfectly smooth)

HHS81 commented 5 years ago

C182T G1000 with KAP140 POH: https://axenty.com/resources/PIM/C182T%20PIM%20(NAV%20III).pdf

More infos: http://oh085.ohwg.cap.gov/operations/training-scenarios---g1000-fits

C182T G1000 GFC700 POH: http://www.rmr.cap.gov/wp-content/uploads/2017/04/cessna-ct182t-nav-iii-turbo-poh.pdf

HHS81 commented 5 years ago

@stuartbuchanan the 182 autopilot makes use of the KAP140 files. It is better to write your own.

HHS81 commented 5 years ago

@stuartbuchanan Why the PFD updates so slow, and where can you cange it? Canvas seems very difficult to make, and the wiki is spammed with quotes instead of usefull informations....

stuartbuchanan commented 5 years ago

Hi All,

I've implemented the transponder - use the XPDR key on the PFD.

The PFD updated at 10Hz by default. You can change that by setting /instrumentation/FG1000/adc-update-frequency at startup time.

Actually, the value is the update spacing, so 10Hz = 0.1. I'm going to fix that so that it is a proper frequency.

-Stuart

HHS81 commented 5 years ago

@stuartbuchanan Since some weeks I´m busy with real life job, 10hours a day at work are the minimum this week. So I`m not able to fix the other issues left here. But it looks like it will be better in at least 2 weeks.

Nethertheless I follow the forum a bit, and I read your comment on the C182S-fdm. The C182S uses real coefficients, and what I read about the left-pushing tendency on the real one I consider the behavior as realistic. You will have a strong left-pushing tendency at full power at very low speeds, decreasing with speed, and increasing again with alpha-deg. At cruise speeds you can take the feets from the pedals, it does not need any pedal input then while turning. What the aircraft makes it more difficult is the constant speed prop and the higher speed. Also it is quite nose-heavy, there had been a lot of accidents where the nose-gear has been slammed into the ground while touch-down. See also: http://www.dviaviation.com/files/45136649.pdf

Maybe I should get back to the forum to answer him directly....

paju1986 commented 4 years ago

Hello. Im tying to implement the left switches panel for this. Im posting the progress on the forums.

https://forum.flightgear.org/viewtopic.php?f=4&t=34571&p=362201#p362201

HHS81 commented 4 years ago

@paju1986 the inactivity you can see here is due to real life. Benedikt has so much as I know family, myself is beside working, back in university to get a master degree.

It looks good, do you use the Flight Manual as reference? Please make sure, that ALL textures needed for the whole instruments panel can be put later in ONE texture map. Less objects, less textures needed makes it easier for lighting maps and of course better framerates!

HHS81 / c182s