-
Posts
22 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Everything posted by foliainfx
-
Did they really overlook the fact that RNP-AR approaches can't be flown with FLS..?
-
Does it work with the normal 2024 version? Try clearing your wasm folder.
-
Please correct wing condensation - comparison real world
foliainfx replied to starjun's topic in Modelling & Texturing
And maybe ini shouldn't be so resistant to advice and facts. My personal opinion but I am sure many will agree. I wonder what their customers think about working less on updates. -
Actually, you are right, I thought you meant the line on the VD indicating the vertical path. Apologies for the misunderstanding
-
Step descents aren't implemented currently, iirc they wanted to implement this at a later point
-
It's dashed when the FCU altitude is different from the CRZ ALT entered, this should also be fixed in the next update already
-
In the next update there should already be a few things fixed (RADIO HEIGHT, constraints). VIEW ALONG ACFT TRK will be implemented at a later point is what I got told previously
-
So your issue is that when you manually tune the frequency, the values get reset?
-
Send an image of your RMP
-
Ini know about this issue, it should be fixed in the large update
-
It's not unlikely they're just straight up ignoring you to prevent you from getting a refund (since the product doesn't work) actually. Wait for a response, if they don't answer within a week ask about it. They've been ignoring my ban appeal for a while now.
-
Try doing a full deinstall, with all files deleted and then reinstalling.
-
The first load after an update/install will be WASM compiling, this will take quite a lot of time compared to other loads. While this compiles you can switch to other tabs just fine. The time varies, it's 10-15 minutes roughly on average.
-
I agree with what you've said. Still my primary focus is that their reference pilots agree with the incorrect model. If those pilots are flying the same spot irl they would in the sim, they are a safety hazard to flight crew and passengers. Their seating position would be too high throwing their flight path angle perception off and can cause issues operating the rudder aswell as instruments. I have attached an image which is according to Airbus a too high seating position. This gets really close to the false position (according to them and their pilots right) in the iniBuilds. I hope iniBuilds will take necessary measures as this is a hazard that should not be happening, especially under several pilots.
-
The A350 only has 4 autobrake types: - BRK MED - BTV - BTV CONTAM - RTO (MAX in other aircraft)
-
iniBuilds know about this issue, it should be fixed in the next update, ini have several issues with the VD since release in terms of correctness
-
Although iniBuilds keep denying this problem, it is 100% the case that the cockpit model is wrong. The correct pilot position in the iniBuilds varies from the real pilot position. The first image shows the seating position that is correct according to iniBuilds, the position however does not show the DU pb. The second image shows an Airbus safety first article (https://safetyfirst.airbus.com/are-you-properly-seated/ fig.1 Eye reference point principle) providing a guide on how to be seated properly during critical flight phases. The third image shows the pilot position seen through META glasses. On both the second and third image two things show: the DU pb are visible and the blind area (see Airbus safety article, fig.7) are the same, while in the ini A350 the blind area does not match the safety article. I have been told that iniBuilds' reference pilots have been flying their A350 in the same position as seen in the first image attached, if this is indeed the case in real life I expect iniBuilds to take reasonable action as an incorrect position during critical flight phases is a safety hazard to crew and passengers.
-
In the iniBuilds A350 the switches look very dark, however they should look a lot more metallic & glossy. All knobs in the ini A350 that should have a thin black part as seen on images, in the ini this is barely present and gray.
-
Fixed this somehow
-
The setup log is attached. SquirrelSetup.log
-
When I download the A300 it downloads and when it decompresses I get an error message and the download stops. Is this a known issue or is there any known fix for this?