Hi dear iniBuilds team,

 

first of all: huge props for the SU4 performance improvements on the A350.

The gains in smoothness and stability are very noticeable, especially on longer sectors and in complex scenery. It’s clear a lot of deep, unglamorous work went into that, and it really shows.

 

Now that performance has taken such a solid step forward, I’d like to suggest two features that would meaningfully push immersion and workflow realism to the next level, especially for users with more advanced setups.

 

---

 

 

1) 

Physical Printer Support (POS 80 / similar)

 

 

Support for a physical cockpit printer (e.g. POS 80–style thermal printers) would be a fantastic addition.

 

Use cases:

 

• ATIS printouts

• OFP / loadsheet

• Weather and route revisions

• Clearances or operational notes

 

Several aircraft already show how powerful this can be for immersion, and the A350—with its strong procedural focus—would benefit enormously from it.

 

---

 

 

2) 

Remote KCCU / OIS (Tablet / Browser / Networked Device)

 

 

A remote KCCU / OIS interface, similar in concept to what Fenix or FSLabs offer, would be a major quality-of-life improvement.

 

Potential benefits:

 

• Entering FMGS data from a tablet via a browser

• Interacting with the OIS (charts, performance, documents) outside the main sim view

• Cleaner workflows for users without perfect mouse access to the cockpit

 

 

Given the A350’s real-world architecture (KCCU + CDS + OIS), a remote implementation feels both technically appropriate and highly immersive.

 

---

 

 

Why now?

 

 

With SU4, the aircraft feels like it has reached a performance baseline where deeper interaction features become viable without compromising stability. These two additions would not just be “nice extras,” but meaningful steps toward a more complete, modern long-haul simulation environment.

 

Thanks again for the work you’ve done so far — the A350 is already an impressive piece of engineering. I hope you’ll consider these ideas for a future update.

 

Best regards, thanks, Claas

would be too cool ...

Hi. I'll take these suggestions and feed them back to the team.
 
For what it's worth, with mobiflight or spad, you can setup about 90% of the KCCU functions that are exposed in the sim (I do this for my WW MCDU) but I agree a native solution would improve things overall. We'll see if anything can be done. Thanks! 

ah interesting ... are such mobiflight profiles to be found on flightsim.to? recently I had the problem that mobiflight won´t recognize my winctrl hardware so I had to count on simapp pro itself ...

 

THANK YOU! Looking forward what the team says 🙂 

any news on this? 🙂