KA350i Version 1.1 (SP1 - 1.1.29) [UPDATED MAY 24]

[SAS443]

It starts and flies with the fuel pumps turned off. is This normal ?

The engines are equipped with both boost pumps and high pressure pumps. Are you talking about standby boost pumps?

[tredsell]

Hi

I can confirm the KA used 6.4Gb VRAM with all systems off at NZQN, and utilising 90% CPU.

That was a suprise, although based on what others here have said, perhaps not quite so much. That is very near collapse on my GTX1080 8Gb graphics card - which can currently access 6.7Gb of my 8Gb VRAM. To its credit though, no CTDs with the KA as yet, at least flying in Colombia earlier today.

By contrast the rather tasty and highly complex FSL A320X Airbus in exactly the same location (NZQN) used 2.9Gb VRAM!

Once we have Win 10 v2004, I believe we'll be able to access 7.1Gb. However, I agree this is a huge amount of VRAM for a GA plane.

ray

Yeh I see on average 6-6.6 GB VRAM usage on sim startup before touching any KA350i systems. I think this is pretty exceptional, hopefully someone might be able to offer some feedback on whether this is being looked into?

I think the couple of CTDs I’ve had were probably when VRAM was exceeded (nothing in event logger) it seems utilising the FMS can cause spikes in usage when entering closure points for airways or ‘direct to’, maybe that same spike is triggering the CTDs for others?

[kevinlee251]

1.1.7 is working fine in P4D HF3 !
after a 1 hour flight from LOWI to LOWS , Version 1.1.7 is close to perfect.
1、The problem that the G / P scale is not displayed only when the ILS frequency is input in NAV1 has been solved.
2、The problem that the dll cannot be applied to this version of P3D has been solved.
3、The problem of directing to a planned waypoint leading to CDT has been resolved.
4、I didn't care about the memory problem, or the memory problem, and there was no obvious stuck or error about memory overflow. Maybe it may happen after some time, this issue will continue to pay attention in the future.
5、No obvious model and texture problems are found. I just think that the high-speed rotating propeller modeling and texture are very simple. This can learn carenado.
6、When establish the LOC signal at a 30-degree cut-in angle, I encountered a positive crosswind of 9 knots. At 160 knots at that time, the aircraft did not enter the course at once like a jet, but was established in reverse. I do n’t know if it ’s the performance of the aircraft, or what.

I hope to see this Kingair in P3D V5, it is this Kingair and FSLABS that I still did not uninstall P4D lol

QQ图片20200423024526.jpg (244.56 KiB) Viewed 40075 times

[FinnJacobsen]

Just made a short flight with this route:
EKBI RW09 SID:ABINO6B ABINO P615 ALS ILS32/SB RWY32 EKSB
P615 consist of: ABINO-RIDSI-ASBIl-ALS

I have modded Trueglas to 2048x2048 textures and Reallight to 1024x1024 textures (Reallight does look grainy though).

The flight went rather smooth with no stutter, no bad FPS or CTD's.

I made a DIR enroute towards ABINO to RIDSI with no CTD (just to check the DIR CTD issue that has been present before)

I did experience some strange things though:

• After start up of the engines using the GPU, I reset the generators, but as soon as I disconnect the GPU, power in the aircraft is lost and I have to reset the generators again. FMS and some avionics looses power, but when power is restored, the loaded flightplan and data is retained - so a small hickup !

• Setting altitude with Baro at QNH, I was not able to increase altitude to more than 5500 ft, wjile I wanted to set my cruise altitude to 7000/FL070 (With TA at 3000 ft)
  After passing TA at 3000 ft I set Baro to STD, now my altitdue setting goes from 5500ft to FL550 and I had !!
  I still thing that the altitude setting acts strange and regard it as a bug.

• Next issue was with the charts (Navigraph subscription).
  I could load the airport overview for EKBI, but I could not load the SID ABINO6B.
  I could also load the Airport overview for EKSB, but could not load the apporach plate for EKSB ILS32.

Conclusion:
The flight was a positive experience - smooth FPS, no stutter.
As described above, I had some hickups with the PL21, electrical system and the charts, but nothing showstopping.

[Taguilo]

6、When establish the LOC signal at a 30-degree cut-in angle, I encountered a positive crosswind of 9 knots. At 160 knots at that time, the aircraft did not enter the course at once like a jet, but was established in reverse. I do n’t know if it ’s the performance of the aircraft, or what.

Were you in a NAV to NAV procedure or just a direct LOC capture? If this last option, then remember to set the OBS cursor to LOC bearing before arming the mode, otherwise the AP will use the current OBS bearing to determine whether it is a LOC or a B/C mode.


Tomas

[Matthieu-C]

I have modded Trueglas to 2048x2048 textures and Reallight to 1024x1024 textures (Reallight does not look grainy though).

I confirm that reducing texture quality or disabling TrueGlass and RealLight improve VRAM usage (86-91% on a rainy day at LFRS).

However, if you reduce RealLight texture quality (1024 x 1024, 2048 x 2048), the display quality becomes poorer (texts on the yoke, texts on some knobs such as BARO / RTU brightness), especially at night (texts on overhead with lights on).

During daytime at LFRS (rainy day), with my PC, TG 1024 x 1024 and RL 1024 x 1024, VRAM usage is 81-96%! Good enough to fly, but quality display is... below standards. Same conditions with TG 1024 x 1024 and RL 2048 x 2048, VRAM usage is 91-92%.

UPDATE: with TG 1024 x 1024 and RL 4096 x 4096, VRAM usage can be low (...less than 95%!) if I switch sometimes between full screen and windowed mode...

[andrew]

Is anyone having issues with the PL21 overshooting waypoints? I was flying a SID out of KPHX...each turn would overshoot the waypoint and then the plane makes a turn to compensate for the overshoot. Any input would be much appreciated!

[Taguilo]

• After start up of the engines using the GPU, I reset the generators, but as soon as I disconnect the GPU, power in the aircraft is lost and I have to reset the generators again. FMS and some avionics looses power, but when power is restored, the loaded flightplan and data is retained - so a small hickup !

Hi Finn,

I'm sorry but I wasn't able to reproduce what you describe. Did you actually move generator switches full up and released to reset them (I guess you did) or just moved to the ON position from Off? I also assume your starter switches were both in off position, and no amber annunciators related to generator were lighted.

Tried all different combinations that I can think of, and it always worked fine.

• Setting altitude with Baro at QNH, I was not able to increase altitude to more than 5500 ft, wjile I wanted to set my cruise altitude to 7000/FL070 (With TA at 3000 ft)
  After passing TA at 3000 ft I set Baro to STD, now my altitdue setting goes from 5500ft to FL550 and I had !!
  I still thing that the altitude setting acts strange and regard it as a bug.

I'm sorry here too, but couldn't get what you state happened to you:

Sprite 7.jpg (98.69 KiB) Viewed 40003 times

You can see transition altitude is set to 3000 ft; Preselector to 5500. Right before reaching 3000, as baro data was flashing I pressed BARO button and Preselector displayed F055.

Sprite 14.jpg (113.48 KiB) Viewed 40003 times

Then I raised the Preselector to 7000 ft, still working fine.

Sprite 23.jpg (97.79 KiB) Viewed 40003 times

Here I set the cruise altitude to 9500 ft, and then repositioned the Preselector to that altitude. Fine too.

Perhaps it might help if you could describe step by step what you did in that situation.


Tomas

[FinnJacobsen]

@Taguilo

I will test the GPU/Generator issue once again - could be an Error40 (User error)

What I experienced with the altitude setting, was that I had set TA to 3000 in the MCDU.
Then I rolled the Altitude setting in an attempt to set 7000 ft, but it stopped at 5500 ft.
I kept it at 5500 ft until I passed TA at 3000 Fft, where I set Baro to STD. As I did so altitude in the PFD ws FL550 and not FL055.

How about the issue with the Navigraph charts ?
The chart for EKBI SID ABINO6B and EKSB APPR ILS32 exist in the Navigraph charts database, but cannot be loaded in the PL21.

[tredsell]

Hi Finn,

Did you disengage the starters? The generators wouldn’t work otherwise

Tom

[jean.procki]

Why throttles and props are not adjustable as in version 1.0.6_200131 ?

Pourquoi les throttles et les props ne sont pas réglables comme dans la version 1.0.6_200131 ?

cordialement

[Taguilo]

What I experienced with the altitude setting, was that I had set TA to 3000 in the MCDU.
Then I rolled the Altitude setting in an attempt to set 7000 ft, but it stopped at 5500 ft.
I kept it at 5500 ft until I passed TA at 3000 Fft, where I set Baro to STD. As I did so altitude in the PFD ws FL550 and not FL055.

Hmmm. I think I know what you did. You rolled the ALT knob with the mouse wheel only, so altitude changed in 1000 ft steps until reaching 55000, which is the highest supported by PL21. Then when you set STD on the baro, value displayed changed to FL550, obviously.
Remember to use left/right mouse clicks to change altitude in 100 ft steps.

How about the issue with the Navigraph charts ?
The chart for EKBI SID ABINO6B and EKSB APPR ILS32 exist in the Navigraph charts database, but cannot be loaded in the PL21.

I will pass this to Development Team as it is not my area.

Tomas

[FinnJacobsen]

I just made a small test to check the issues I had.

1. Generators got online correctly - so seems to be my fault.

2. The baro/STD seems to be my fault - as You said - I probably had it dialed up to 55000 instead of 5500, so it became FL550 - My fault.

3. Navigraph charts still have issues with the EKSB ILS32 approach - but it can load the RNV approaches fine - maybe a bug with the Navigraph chart vs Navigraph Airac.

[lukasz]

Any plans to P3D5?

[Ephedrin]

And here we go again... seriously, I'm running out of patience.

The engine control levers have been working until this SP1. The throttles don't go into idle and beta AGAIN, the Prop1 lever snaps into feather after every movement AGAIN and I really don't have the time and will to tweak, search for help or fix things every time I try to start the Kingair or installed an update..

PLEASE!

WHAT for God's sake do I have to adjust NOW or what do I have to use to assign NOW to use this airplane???

I use one lever for every control, so six levers in total. They are assigned via FSUIPC's "send to FS as normal axis" as before and the detents are set through MVAMS. No FSUIPC calibration is applied. The axis.cfg is not read only, the values set by MVAMS are saved. Everything is set as it was with the 1.0.6 version, it just doesn't work. And I'm really really tired to search through dozents of forum pages..

Thanks for any help..
Marc

Edit: 4.5HF2.