[Hunter Helicopter - Some questions and concerns based on previews...]

10 hours ago, Loki said:

Hello,

Apologies for no reply here.

Of course we care and we sincerely apologise if you feel that isn't the case. I've forwarded the list in the original comment to the team and we'll take a look at what can be done. Thank you and I hope you are enjoying the product if you got it 🙂

 

Loki,

I appreciate the update and notification that the concerns were sent to the team. I'm also tracking developments and statements from representatives both at Avsim and on the MSFS official forums, and am excited to hear strong consideration for a more fully-featured and accuracy-focused model. I hope that is seen to fruition. Thanks again for the update. 

[Hunter Helicopter - Some questions and concerns based on previews...]

It looks like it was released with a lot of issues unresolved other than strut stance. Can I get the courtesy of a response to the other concerns? I see from other support issues with other KF aircraft they perhaps they don’t care to respond often to customers?

[Hunter Helicopter - Some questions and concerns based on previews...]

KF Team,

I've been watching with interest following the announcement of the "Hunter" helo that's allegedly coming soon. I understand that I should not expect DCS AH-64 fidelity, but I noticed a few things that to me are glaring, and am wondering if you guys are still at the "accepting feedback" stage, especially if the feedback is, at least in the opinion of myself and a few people I've talked to, reasonable to attend to:

1. The depicted aircraft seems to lack landing gear strut compression, or compression to the degree that is appropriate for a fully loaded and fueled helicopter of this type compared to images of the real thing. Do you plan on adjusting the helo's stance on the ground to show increased gear compression so it doesn't sit too nose-high?

2. On the HMD, it looks like the compass heading you're on, plus the airspeed, the vertical speed, and the waypoint DME display all have black backgrounds on them. As it's a HUD-like HMD, the background for all numeric displays should be transparent. Also, color-wise your choice should be consistently green for the HMD, no blues and reds. 

3. For the keypad on the left side of the cockpit, it appears that the screen is correctly black in color while the system is off, but once powered on, I'm seeing a beige screen with black letters/numbers. Can this be changed so that the screen remains black, and that the letters/numbers are yellow-green? (same color as the main-panel advisory/warning display text)

4. I have yet to find a picture where the standby/backup instruments are encapsulated as one digital display. All images I'm showing show a three-gauge cluster of analogue black and white attitude indicator, along with analogue altitude and airspeed indicators. Can this be adjusted, or can you provide an image showing the helo in real life with this type of digital display? It stands out due to it's colorfulness and fidelity as out of place compared to the tech in the rest of the cockpit. 

5. On some preview videos and images, I'm seeing a desert-themed livery that seems like it's 90% towards an Israeli depiction, but missing the markings. Will this be fully completed as an Israeli one? 

I'm not focusing on systems outside of the above visual depictions as I understand that may be out of scope for this project, but I think the above are minimum-viable basics. 

Looking forward to seeing more on this project in the coming weeks!

[Bell 47J Support?]

Greetings,

I know it was just released, but will there be a subforum introduced for any needed support for the Local Legend Bell 47J Ranger, which was stated to be produced in cooperation with iniBuilds? 

I anticipate purchasing the aircraft shortly after perusing some reviews, so I don't require support at this time, but I'm noting so far that the only main threads about it are on the Official Forums.

In my experience with reporting bugs to a variety of developers, more than one have quietly preferred to receive feedback directly, as...again...more than one dev seems to have discovered that they are not consistently getting feedback/bug reports from the Official Forums reporting mechanism / via Asobo and MS. 

Thank you. 

[KMDT (Harrisburg) Question/Issue]

For what it's worth, I tried multiple times to reach out to SierraSim since their KMDT release last fall with no response to email or through their official support form on their website. I recommend using the newer and MUCH better Xometry version instead. 

[AI Parking Radius for Gates A13-A19 is still too small.......]

On my end, A1-12 lack aircraft, A13-20 and B and beyond work fine with Hawaiian B717s that I mapped from AIG to be used by FSLTL. Just the terminal "bump out" near the highway for the initial A-gates is lacking on my system. 

[AI Traffic Parking Radius]

Greetings,

I am *hoping* that the team was notified by now, but in consultations with the AI experts at AIG (and others), it was noted that the gate parking radius parameters (across the airport) are insufficient for some classes of aircraft - particularly heavy jets, with users consistently having issues with aircraft disappearing and reappearing while at the gate.

AIG has said that inibuilds has not made the gate radiuses wide enough to support their traffic at this and other airports. There is also a known Asobo constraint with ground vehicle parking positions that also causes disappearances, but it seems like this can be partially mitigated (not fully, but an improvement) with parking radius parameters that align with "industry standards" from AIG and FSLTL. 

https://www.avsim.com/forums/topic/637372-inibuilds-honolulu-released/page/4/

Looking forward to forthcoming updates.