100% SWS have worked on getting this realistic.
If may be a bit tricky but that’s just how it is.
1 Like
Yeah I really like the Kodiak and level of detail is impressive but the yaw made the aircraft uncontrollable at takeoff and required the Autorudder assist (total departure from reality there. There is a fix from Simworks which would be great to have, but I have been unable to download it from the Direct Download link in my account (it barfs repeatedly at 107MB Done) and the Alternate links download links are also broken, It’s been this way for days and no response from support yet. So while its desireable to use the Simworks solution, I’ll go with an alternate for now that is at least accessible.
1 Like
I’m posting this here because the original thread got closed for some reason. I have encountered the following problem. I have the aircraft follow the GS on autopilot (approach mode). The autopilot adjusts the elevator trim to follow the glideslope. So far so good, but as I disengage the autopilot the elevator trim often jumps (I don’t know does it jump to the trim value before engaging the autopilot or what), immediately destabilizing my ILS approach… Anybody else observe this? What to do about it?
2 Likes
Yep, I’ve experience that as well.
1 Like
Hmm, Kodiak seems to lack some performance in VR vs other bush aircrafts. Even that i disable that small screen, autopilot, propeller and its heat steam and co pilots mfd, i still got 5fps less 45-46) than CJ4 (49-51fps) without modding cj4. Best result i did got with highly modded tbm with 52-55fps (disabled all the big screens, propeller and the heat).
It didn’t require it, but you did have to take-off in a certain way. Pulling too steeply on rotation would send you into a spiral.
Have you tried a different browser? I just tested the three links I can see, and the middle one does not work for me. The “Direct Download” one works fine, and the top “alternate” link works, although it makes you jump through hoops to do so, with several re-directs.
Yes, that works for me. Either just over the detent so Beta just appears on the PFD, or all they way back in to full reverse.
Have you tried mapping “hold reverse thrust” instead of toggle? A few of us regularly fly Caravans in a group flight performing very short field landings and hold is far superior to toggle when it comes to reverse thrust engagement reliability. Just hold the button for as long as you want reverse thrust to work.
It does work midflight.
I also use a joystick with a throttle and for the Kodiak I use the default F2 key “decrease thrust”. Holding it down goes into Beta then reverse. To come out of reverse just give it a bit of throttle. I also use it sometimes for Beta when taxiing.
I noticed the same thing. I would feel like the CJ4 should be heavier in VR due to all the screens and avionics but not really.
When I fly this plane in VR I can’t see the dots on the AOA indicator unless I put my head right in front of it. Anyone else having this problem and knows how to fix it?
1 Like
The fact that my answer to your question is “What AOA indicator?” suggests you are right. I haven’t seen any AOA indicating lights in VR from the pilots seat, ever.
1 Like
Out of interest I have to say I have the exact same issues as you have described, using a joystick hatswitch for toggle reverse thrust. I have had several embarrasing crashes due to pusing full throttle, when i hoped rather than looked down and checked, that I was in full reverse.
Yes it does only seem to work in this config, once you are established on the ground. I too, thought it must be an aircraft limitation but it would seem not.
1 Like
I facebook there was suggestion to unbind throtle axis from throtle controller, and bind throtle controller axis with throtle 1, throtle 2, throtle 3, throtle 4 with all of them
There are a lot of performance affecting factors, these are not only the screens.
Compare both with a more detailed method and you’ll find the answer to your question.
- Separate aircraft performances measured on MainThread and GPU latency in the same environment (same place, weather, speed and altitude, etc.)
- Check what happens when you turn the displays, heat, etc. off.
- You will find out which component of your PC lacks the performance and reaches it’s boundaries causing FPS loss.
Kodiak is more complex than the built-in planes even with mods. I expect your CPU to be the bottleneck but check it for yourself to be sure about it.
Close to the ground (where bushplanes usually operate) the load on your PC is a lot higher. Drawing a lots of objects especially with high terrain LOD puts a lots of load on the CPU.
2 Likes
Yep tried all that but still broken, I hear the issues are being worked on but nothing more would kinda like to at least get a ticket acknowledgement even if not fixed but then again if the there are hundreds of tix in the queue that may take a while.
I do a similar thing, I’m running the Bravo Throttle and use SPAD.Next. The power lever provides full range from BETA up to max power. I use the power lever detent to get into reverse thrust and the TOGA button (held) to ramp up reverse to max. Pulling back out of detent goes back to powerlever=zero. Feels natural and prevents the accidental application of reverse thrust. I do some checks to ensure the power lever is at 0 and prop is in BETA when going into detent to ensure the powerplant is in the right state.
1 Like
Hi all,
What’s the preferred/correct way to complete a power reduction? For example, upon reaching cruise altitude. Say I’m aiming from 1250 TRQ and 2100 NP/RPM.
Set torque first and then set NP? Other way around? Or should I be setting by a different parameter (ITT?)
Cheers.