apollon01

Hello, to support my feedback regarding the flight model with some concrete numbers, I ran few tests for climb and cruise performance. Climb As per available resources from Jim Savage including his video below, the climb profile should look like this: 32.5'' MP 2000 rpm 1000-1500 ft/min climb resulting in ~100 kts climb speed. However, if the iniBuilds Spartan is let to speed up above some 130 kts after take off, the speed starts increasing rapidly resulting in climb speed of almost 190 kts with the engine parameters set as above. Cruise Jim Savage's video below shows his cruise profile as follows: 26'' MP 1900 rpm 8500 ft altitude resulting in ~140 kts cruise speed. However, the iniBuilds Spartan ends up cruising at nearly 190 kts under the conditions above: As mentioned in my feedback related to the flight model, it looks like the problem is related to the fact that once the speed builds above some 130-140 kts, it sort of becomes uncontrollable and the aircraft usually settles to about 180-190 kts in climb or cruise with the power setting not having much of an impact on it. Will you please have a look into this? Thank you.

Hello, I am perfectly happy with the vintage way of night lighting of the panel in the classic Spartan. For the modern cockpit, let me please suggest appropriately modern panel night lighting - backlighting of individual gauges. I suppose that if the panel of a Spartan was brought to more modern standards, the night lighting option would include lighting of individual gauges. I have no idea of how easy / work intensive such a feature is, of course. Though, I believe it is a meaningful suggestion 🙂 Thank you for listening.

Hello, Will you please consider replacing the COM3 & NAV3 radio (which is not connected to any gauge anyway) with an ADF radio? The ADF radio could be linked to the yellow needle of the RMI gauge (which is INOP anyway in the version 1.0.3). The avionics could follow the logic below: GNS530 - NAV1 - HSI GNS430 - NAV2 - RMI green double needle ADF - RMI yellow needle Thank you for considering this suggestion!

Hello, noticed that the fuel computer screen is misaligned with the unit in the MSFS2024. MSFS2020 seems to be OK. MSFS2020 MSFS2024

Hello, a summary of how the GNS530 / GNS430 are programmed in MSFS2024 / MSFS2020. The message is that their functioning is not consistent: sometimes GNS530 is NAV1, sometimes NAV2; sometimes the GNSs can be switched between GPS/VLOC, sometimes not; sometimes they are connected to a gauge, sometimes not. The differences depend on the panel (modern, classic with GNS) and which sim (MSFS2024, MSFS2020). Legend: NAV1 / NAV2 column: shows whether the GNS unit appears as NAV1 or NAV2 radio GPS / VLOC column: shows whether the GNS unit can be swapped between GPS / VLOC (both) or is locked to VLOC (VLOC only) or actuates on a different GNS unit linked to gauge column: shows to which gauge the GNS unit is connected The weird thing is that in MSFS2024, the GNS430 unit can sometimes be swapped between both GPS / VLOC modes but sometimes is locked to VLOC mode only. I conducted a number of tests but was not able to isolate what causes the unit to lock on VLOC only. Will update this thread if I find the cause.

Hello, some additional feedback regarding the flight model. Applicable for both MSFS 2020 as well as MSFS 2024 versions. Roll rate seems to be rather slow. I can only speculate here of course as I've never flown the real thing. Pitch is quite unstable with the VSI all over the place all the time (please refer also to my feedback regarding the modern cockpit avionics) Is the performance right? According to the info available, the Spartan's max cruise should be about 190 kts. However I can see close to 200 kts with 24 inches MP and 2000 rpm. Acceleration to about 140 kts seems fine. From about that point, the speed builds very quickly (even when climbing) and power setting does not seem to have much effect. Bleeding the speed (slowing down) is difficult. Descending at 180 kts at 3 degrees profile had me close the throttle entirely. Slowing down from 200 kts speed to landing gear, belly flap and flap extension speeds is very difficult. Once you slow down with everything hanging down from the aircraft, the back of the power curve is very steep (requires a bit too much power to stay airborne, in my view) The Spartan is pitch unstable. With no pitch inputs it goes from -2000 fpm to 2000 fpm in no time. Difficult to trim it in pitch for any regime of flight (climb, cruise, descent). Requires constant pitch inputs from pilot. Pitch is unstable to the point that the oscillations actually get worse if you let them develop. Thank you for the Spartan. Thank you for listening to user's feedback and I hope you will eventually address the issues reported. Regards, Milan

Hello, here is my feedback regarding the avionics in the modern cockpit. I first posted it the Feedback forum but then decided to re-post here below so that you have the feedback regarding the Spartan in one place. MSFS 2024 version, "modern executive" cockpit. GNS430 is NAV1. Usually in the dual GNS panel, the bigger GNS530 is NAV1 and the smaller GNS430 is NAV2 (which is how it is configured in the MSFS 2020 version, btw). GNS530 is NAV2. It can’t be switched from GPS to VLOC (when pushing the CDI buton, it actually swaps the GNS430's GPS/VLOC instead), it is not connected to any gauge (likely it should be connected to the RMI but none of the two needles move in relation to the GNS530 inputs). The NAV3 analog radio can’t be tuned because it does not react to mouse inputs. The RMI gauge needles do not move no matter what. Turn coordinator needle shakes unnaturally, especially when on the ground Fuel needles did the same for a while and then stopped. VSI gauge seems a bit restricted since it reads only up to +/- 2000 ft/minute with linear scale. It looks like making it up to +/- 3000 ft/minute on non-linear scale would help to get rid of its jerkiness. Just checked quickly the MSFS 2020 version for the avionics and: GNS530 is NAV1 and it is connected to the HSI. However, it is constantly in VLOC with no change when CDI button is pushed (it goes momentarily to GPS and then immediately to VLOC again) GNS430 is NAV2 (as opposed to NAV1 in the MSFS 2024 version), can be swapped between GPS/VLOC but does not seem to be connected to any gauge. The NAV3 analog radio can be tuned and frequencies swapped but it does not seem to be connected to any gauge. As a result - the RMI is just sitting there doing nothing as in the MSFS 2024 version. I LOVE the modern cockpit and think it is a pity that it works only partially because the Spartan has s potential to be a great tourer. I would appreciate if you could address the issues above. Please consider also documenting in the manual how to hide the phone EFB (by the screw on the ASI gauge).

Hello, here is my additional feedback regarding modelling and texturing of the Spartan. The issues are applicable to both MSFS 2020 as well as MSFS 2024 versions. Texture in the cockpit turns black when the phone EFB is hidden - only in the Modern Executive cockpit Screws on the edges of the panel in the classic cockpit are popping out = float above the panel (in VR this is really noticeable). This applies to the classic cockpit without the GNS430. When that is added to the cockpit via the phone EFB, the whole panel moves a bit towards the pilot and the issue with popping screws disappears since the screws do not move (only the panel does). Thank you, Milan