Jump to content

richboy2307

Moderator
  • Posts

    169
  • Joined

  • Last visited

  • Days Won

    8

Posts posted by richboy2307

  1. On 4/14/2024 at 3:20 PM, UpUpandAway said:

    After this morning's hotfix was downloaded, the issue is fixed, thanks!

    Yeah that was a backend issue still pushing out the older version. Version 1.1.1 HF1 should be the update that was *actually* supposed to go out with the fixes as listed in changelog 🙂

    • Thanks 1
  2. Thanks for your post.

    People with real world experience on the type are consulted throughout the development process. Naturally, as the product matures and the userbase expands, so does the product's exposure to even more individuals with varying real-world experience on the type to those initially consulted. The feedback naturally also evolves into more specific items and we continue to improve the product on the basis of this feedback.

    We're sorry if improving this product and taking action on user bug reports has brought any inconvenience to you.

  3. What are your scenery config options? Does this also happen with items like "Terminals - People", "Landside Cars" & "Animated Airtrain" disabled?

    Here is a video of me floating past in drone cam with no noticeable immediate change in FPS across this area. (Specs: AMD 5800x3D. RTX 3090, 32GB RAM)

    Maybe if you can share similar videos with the FPS Counter (enabled in via Developer Options > Debug Menu > Display FPS).
    Also try to clear your scenery indexes, reduce Terrain Level of Detail settings (100 or lower) and empty you rolling cache (if using any). 

    For clearing scenery index: 

     

  4. On 4/20/2024 at 6:00 PM, kasen said:

    I've attempted three flights, none successful:
    - Barcelona-Dubai, when I was about 200nm away, the plane just froze, only the steering worked, no lights, screens frozen... I had to land visually... 200nm from the destination.
    - Dubai to Barcelona (first attempt): the flight went well until Italy, where the plane shut down and started turning sharply to the right, couldn't recover it at all, straight to the ground. Everyone died.

    - Dubai to Barcelona (second attempt): the flight was quite good until around Sicily where the plane shut down again, mysteriously recovered at 10,000ft above the ground, continued normally but then, while landing, it shut down again, and to the ground, impossible to recover (everyone died).

    Sorry for your bad experience. It would help us better if you gave more information of what you did prior to each instance of crash?
    What you have written here is telling us what happened *after* the crash.  But in order to try to resolve the issue, we need more information on what you did just *before* it crashed.

    For example, did you change something on the MCDU? Did you change an autopilot mode, or changed some speed/heading/alt data on the FGCP? Was there a weather update just before? etc

    Thanks!

  5. On 4/20/2024 at 1:44 AM, LRJETPilot90 said:

    I am not compensated by inbuilds in any way, shape, or form. I understand that it computer programming can be so fickle because there are infinite hardware/software configurations to try and plan for. The sample size of users experiencing the issues "may" be relatively small compared to the number of copies sold. What I do not understand is why the testing is being pushed off on the customer. I have a day job, flying airplanes. During my time off, I choose to load up an airplane and fly it across the country. I have done so without incident using other add-ons for years. I do not understand why this airplane is the exception. I'm curious to know how many people just put the plane down when this sort of thing happens and don't bother to report anything. The quality control has to improve.  I realize that it may not come off this way, but I mean this in the most constructive way possible - I genuinely want ini to succeed, because companies with your capabilities are great for the hobby. But I don't think dedicating multiple paid testers to trying to reproduce major (in consequence) outliers is too much to ask - have them test scenarios throughout a week testing phase putting the airplane through its paces. 

    Thanks for your report and constructive criticism!
     

    On 4/19/2024 at 3:07 PM, richboy2307 said:

    In the absence of being able to reproduce the issue ourselves or through our testers, we need more data to try and figure out what may be the cause.

    But I believe you misunderstood what I wrote above.

    We do engage in extensive testing internally, and do use a combination of internal and external testers for the same. While I can't share specific metrics regarding the testing process, rest assured that we have been taking measures to improve quality control, and do engage in testing of our products even post-release. My hiring specifically as a tester is just one such example of  the measures taken.

    I have personally completed over 28 flights of various lengths on the latest version alone without such CTD issues (Yes I know, I am just a sample size of 1, doesn't mean much.)

    Unfortunately, through this process of our internal and external testing across versions we have not till date been able to reproduce these issues. We will continue to fly our planes and test future iterations, but if we cannot experience the issue across any of the systems and persons involved in testing, then how are we to even understand the cause of the issue, let alone try to fix it? 

    We fully appreciate our users are not compensated for testing. We also do not expect them to be testers of released versions of aircraft, but due to the circumstances above, and the nature of this issue we do not have a way forward without additional user cooperation from those affected. So to that end, thank you and everyone else who puts up their valuable personal time towards using and reporting problems with this product. 🙏
     

    On 4/20/2024 at 1:44 AM, LRJETPilot90 said:

    To summarize my flight parameters from the other night (that resulted in the failures/issues previously listed), in the interest of cooperation:

    Thanks, this is just the kind of information we need in order to try and recreate the issue across systems. 

  6. @unhinged_aviator Ok so that's simply external airport ambience that is being heard there - It's under the 'system' sound channel on the EFB as it's tied to the main cargo door operation. We could possibly change it to 'environment' sound channel so you may turn it down on the ground whilst still enjoying other system sounds.

    I'll pass on the feedback, thanks!

  7. 17 hours ago, MarcusVT said:

    Yesterday I had a throttle problem. Autothrottle was working, but when I deactivated for landing, it went to iddle. No throttle input was being sent to the game. I could GA using AP. Then recalibrated throttle, cycled A/T several times and sudenly all came back to life.
    BTW I was always arriving too high for landing and now I turn of A/T to control approach speed. Also set altitude constraint to AT and not AT or ABOVE, for final fixes so that I can arrive at proper altitude. I'm enjoying the plane but, if it is not a real plane characteristic, the VNAV should be improved.

    As for VNAV, yes that is still a WIP and will come as part of a larger improved VNAV system.

    For the Autothrottle, can you confirm when you notice this that the EFB throttle calibration page is still detecting throttle input? This sounds like an issue that was addressed in v1.1.1, wherein if you accidentally clicked the clickspot on the reverser's lever (on the pedestal) in-flight, it would limit the throttles to the reverser range. However because reverser's are locked in-flight, the throttle just appears "Locked" in idle position. The fix is to toggle reversers (via hardware button or by clicking the same clickspot). 

    In v1.1.1 the clickspot of the reverser was disabled when airborne. Should only be clickable on the ground. Please confirm, thanks!
      

    • Like 1
  8. 20 hours ago, Matteo Spacca said:

    but this falling out of the sky/fuel/unrecoverable failures have been there since Day 1.

    I have been a user of this product just like you long before working for IniBuilds. Yet I have not experienced random/mid-flight issues like this even once since Day 1. The only crashes I experienced were to do with MCDU  (e.g. when DIR TO/Deleting a hold froze it). A lot of which have been addressed and continued to be worked upon.

    This is not to say the issues you mentioned do not exist. What I'm trying to illustrate is that it is rare and difficult to reproduce. For every one of you facing such issues, there are tens of others who are not.

    In the absence of being able to reproduce the issue ourselves or through our testers, we need more data to try and figure out what may be the cause. That is why we take these reports seriously, but need more detail and the cooperation of users to engage in troubleshooting on their end to help resolve.

    What can you do? Troubleshooting such as :

    • Do a flight without any other addons, only the A300 in your community folder, to see if there are other addon conflicts.
    • Delete the contents of your "work" folder after a fresh re-install to ensure no corrupted data
    • Make these flights in default "White" or "Inibuilds House" liveries to eliminate any "bad" livery files causing conflict

    And when you do encounter the issue, report with:

    • Screenshots/Videos of the failed systems or anomalies you notice
    • Write-up of the things you did just prior to the crash (e.g. what you clicked, what you interacted with, what control inputs you gave etc)
    • Route information & navdata used (E.g. Navigraph data -  KLAX/24R LADYJ4 CSTRO DCT DUCKE DCT LMT DCT MOXEE TMBRS2 KPDX/28L )
    • Any extra things you noticed just before to the crash (e.g. momentary sim-freeze, abrupt winds change, sudden weather update etc.)

     

    All this allows us to try and recreate your flight to see if we face the same issues or find common conditions across reports to try and nail the issue.
    Your patience and understanding is greatly appreciated.

    Thanks!

×
×
  • Create New...