Kodiak Released

[cheezyflier]

Thanks guys! Downloading the paintkit right now. I'm contemplating on doing some camo-paints for this...:ernae:

if you release a camo paint for this model i will put you near the top of the waiting list for my new best friend.


if this add-on doesn't win some sort of award this year, either the competition was rigged, or some developer out there is holding back something that would break new ground.

***i just ate some raisinettes, and it seems like every time i do there is a hard one in there. i'm always afraid to spit it out to see what it was....

 

[DB93]

Hi all.

Lionheart, I have a couple of small issues/questions that I wanted to run by you concerning the event ids that trigger the cockpit controls.

Recently, I built a button box (for lack of a better word) to assign additional FS functions to (things like lights and such). Last night and today I've spent some time deciding what I wanted to map to which button, and then adding the events to the appropriate button in the standard.xml file. After adding and testing a few events, I've noticed that a couple are not properly activated on the Kodiak on the correct event. I don't know if these are bugs or are working as intended, so I thought I'd run them past you to get your take on it.

First is the cabin lights switch. I assigned the event id TOGGLE_CABIN_LIGHTS to one of the buttons on my button box. When triggering the button, the switch on the VC and 2D panels does not change position. However, when I trigger the TOGGLE_WING_LIGHTS command, the cabin lights switch then activates (in both VC and the 2D panels.)

Second are the panel lights switches. When triggering the PANEL_LIGHTS_TOGGLE event, the left-most panel light knob turns on, while the right-most knob does not. The panel lights do not come on until I manually turn the right-most knob. After some playing around, I've found that the right-most panel lights knob is triggered by the TOGGLE_RECOGNITION_LIGHTS command instead of the PANEL_LIGHTS_TOGGLE command. Again, not sure if this is a bug or if it's by design, so I wanted to just run those questions by you. In both cases, it's easy enough to work around by assigning the additional corresponding command to an Up event in standard.xml, but I don't know what, if any impact that may have on properly triggering the lighting systems of other aircraft.

Thanks for any info on this, and once again, great, great plane. I simply love flying it!

-George

 

[Lionheart]

Ok... seriously... this has to be one of the most amazing addons ever created Just been flying it in and out of small strips and the performance is just excellent. Very frame friendly yet beautiful model. First glass cockpit that does not bring my computer to it's knees. Congrats! This might take the number one place in my hangar from my Pilatus Porter.

Thanks BushPilot for the kind words.

:ernae:


Bill

 

[Lionheart]

Hi all.

Lionheart, I have a couple of small issues/questions that I wanted to run by you concerning the event ids that trigger the cockpit controls.

Recently, I built a button box (for lack of a better word) to assign additional FS functions to (things like lights and such). Last night and today I've spent some time deciding what I wanted to map to which button, and then adding the events to the appropriate button in the standard.xml file. After adding and testing a few events, I've noticed that a couple are not properly activated on the Kodiak on the correct event. I don't know if these are bugs or are working as intended, so I thought I'd run them past you to get your take on it.

First is the cabin lights switch. I assigned the event id TOGGLE_CABIN_LIGHTS to one of the buttons on my button box. When triggering the button, the switch on the VC and 2D panels does not change position. However, when I trigger the TOGGLE_WING_LIGHTS command, the cabin lights switch then activates (in both VC and the 2D panels.)

Second are the panel lights switches. When triggering the PANEL_LIGHTS_TOGGLE event, the left-most panel light knob turns on, while the right-most knob does not. The panel lights do not come on until I manually turn the right-most knob. After some playing around, I've found that the right-most panel lights knob is triggered by the TOGGLE_RECOGNITION_LIGHTS command instead of the PANEL_LIGHTS_TOGGLE command. Again, not sure if this is a bug or if it's by design, so I wanted to just run those questions by you. In both cases, it's easy enough to work around by assigning the additional corresponding command to an Up event in standard.xml, but I don't know what, if any impact that may have on properly triggering the lighting systems of other aircraft.

Thanks for any info on this, and once again, great, great plane. I simply love flying it!

-George

Hey George,


No worries. But, I have to tell you, there is a popup window with all the switches on it already. You did know that, I hope. I think its Shift / 2.


On the lights in the cabin: In order to have instruments, forward dome light, and aft dome light run on 3 different circuits, I had to get a bit imaginative. This is because there is no such circuit for 'forward dome light' and 'rear cabin dome light'. What I used were extra circuits that exist that are rarely used, like the logo light circuit, etc. I created animations that have tooltips that read what they do, but actually run a different circuit, such as 'rear dome light' is actually logo light, etc.

Let me know if you have any other questions.



Bill

 

[bushpilot]

if you release a camo paint for this model i will put you near the top of the waiting list for my new best friend.

How's this?(WIP):

Paintkit is so good that it does not take long to create paints.

Will probably add even more wear and tear to this...

 

[DB93]

Hey George,


No worries. But, I have to tell you, there is a popup window with all the switches on it already. You did know that, I hope. I think its Shift / 2.


On the lights in the cabin: In order to have instruments, forward dome light, and aft dome light run on 3 different circuits, I had to get a bit imaginative. This is because there is no such circuit for 'forward dome light' and 'rear cabin dome light'. What I used were extra circuits that exist that are rarely used, like the logo light circuit, etc. I created animations that have tooltips that read what they do, but actually run a different circuit, such as 'rear dome light' is actually logo light, etc.

Let me know if you have any other questions.



Bill

Hey Bill,

Thanks for taking the time to respond. Yep, I'm aware of the light panel, I'm just trying to program my 'button box' to control things like the lighting systems. I just wasn't sure if these were bugs or intentional, and hearing how you've had to get creative for the customized lighting systems, it makes sense that you had to do it that way. As far as the logo and wing lights, do you happen to know off-hand whether these lights are actually present and used on any GA aircraft? I don't fly the heavies at all, so as long as I don't need them for any other aircraft, I can just double up the commands (ie for the cabin lights, I'd use the cabin light toggle command for the down event and the wing light toggle for the up event on the same button.) Otherwise, I'll just program them all as separate buttons.

Thanks again for the information.

-George

 

[cheezyflier]

How's this?(WIP):



Will probably add even more wear and tear to this...

schwiiiiinnngggg!!!! pretty cool

 

[Lionheart]

Hey Bill,

Thanks for taking the time to respond. Yep, I'm aware of the light panel, I'm just trying to program my 'button box' to control things like the lighting systems. I just wasn't sure if these were bugs or intentional, and hearing how you've had to get creative for the customized lighting systems, it makes sense that you had to do it that way. As far as the logo and wing lights, do you happen to know off-hand whether these lights are actually present and used on any GA aircraft? I don't fly the heavies at all, so as long as I don't need them for any other aircraft, I can just double up the commands (ie for the cabin lights, I'd use the cabin light toggle command for the down event and the wing light toggle for the up event on the same button.) Otherwise, I'll just program them all as separate buttons.

Thanks again for the information.

-George

Hey George,

They are stock circuits, like Landing Lights, Nav Lights, etc. Many planes use these circuits.

Bill

 

[Lionheart]

How's this?(WIP):


Paintkit is so good that it does not take long to create paints.

Will probably add even more wear and tear to this...

Awesome!!!!

Looks brilliant BushPilot!




Bill

 

[bushpilot]

Awesome!!!!

Looks brilliant BushPilot!
Bill

Thanks! Here's another WIP. Just a quick idea that popped to my head while making the camo-paint. Suits the character of this aircraft I think:mixedsmi:

Regards, Pekka

 

[Lionheart]

Dang! You are really on a roll there! Nice rescue theme.



What is the name of that Font, if you dont mind me asking?



Bill

 

[BananaBob]

Cool! Nice again! , I always like'em dirty! :ernae:

 

[bushpilot]

What is the name of that Font, if you dont mind me asking?

Bill

USAAF Stencil, free font from dafont.com

http://www.dafont.com/usaaf-stencil.font

Good looking font for this type of paints... although it misses some characters.


Regards, Pekka

 

[doublecool]

Bushpilot, those are Lookin good :ernae:

Yes, dirty... completes her... LOL

 

[BananaBob]

Real world photoreal paint WIP. :ernae:

 

[bushpilot]

Wow. Awesome! I love photoreal paints... they give aircraft sort of dimensions that are hard to achieve in regular paints.

BTW, what font was used in paintkit for wings?... it keeps complaing about fonts being missing every time I open them.


::edit:: I found it, Eurostile....

 

[Lionheart]

Real world photoreal paint WIP. :ernae:

Nice Robert!

That, I believe is the Missionary Aviation Fellowship bird in twin blue stripes, delivered recently, their first order.

MAF started the Missionary Pilots group ages ago. They also sponsored the design of the Kodiak. So that is a famous paint scheme you have done.




BushPilot,

Yes, Eurostile. There are several new 'freeware' fonts out that you can use now that look just like Eurostile. Google Eurostile fonts and you will find them. I can get you the names of the versions I have.

I love that font. They used it on Lotus Esprit and Range Rover early car dash boards.. Looks very modern, yet clean cut.


Bill

 

[cheezyflier]

the chrome spinners look really nice

 

[Fireball6]

Wow - the WIP-Shots looking great gentleman - bushpilot, may i request a Repaint in CDF-Colors or Conair-Conair or another Aerial-Firefighting Operator ? I think the Quest will be a great Lead-Plane for the Fire-Cats. It can also used for the Transport of Smokejumpers.

 

[pontiuspilotus]

Just to add information. I have noticed the same problem with prop rpm controll. (I have 2.2) Prop rpm is too high even when set at 80%. Reducing prop rpm % has no effect until it is reduced to 20 - 30% which doesn't seem right. In other words it stays at about 1800 rpm through the settings of 80% down to 25% or less.

JPMouse, do you happen to run 64-bit Vista? I am using Build 2.2 but still have this prop RPM issue, i.e. reducing prop RPM does not result in a lower RPM (it stays constant).