Jump to content

richboy2307

Moderator
  • Posts

    201
  • Joined

  • Last visited

  • Days Won

    12

Posts posted by richboy2307

  1. On 4/11/2024 at 9:53 AM, Jacky55456 said:

    and this door is always open on the passenger PW variant

    Should be fixed as of 1.1.1 HF1.

     

    On 4/11/2024 at 9:22 AM, Jacky55456 said:

    look at the main gear you can see the hit the frame

    Thanks for the video. I'll pass on the feedback.

  2. Hi,

    On 4/16/2024 at 3:23 AM, Vee1rot8 said:

    should this texture pack be reinstalled after an update to the A300?

    Yes it is recommended to re-install after every update.
     

    On 4/16/2024 at 3:23 AM, Vee1rot8 said:

    Does removing the texture pack actually uninstall the entire aircraft or is this just a mis-communication?

    Yeah the prompt is worded wrong. I'll raise this with the team. It should only delete the optimised texture pack (i.e. the  "inibuilds-aircraft-a300-600-lowtextures" package from your community folder).

    Thanks!

    • Like 1
  3. Hi @MD82, can you check if you are still experiencing this as of v1.1.1 HF1? Specifically, the "HF1" part as the 1.1.1 that released originally on 13 Apr did not have CTD fixes as to amending procs/hold in it correctly. Thanks!

    • Like 1
  4. Can't say i've seen this before. Do y'all have any keybind that you are using for the FD per chance? 

    Also are you able to re-engage the FD1/Standby Horizon afterwards, or its completely unresponsive?

  5. 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
  6. 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.

  7. 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: 

     

  8. Hi @Michele

    • TOGA button: Clickspot has been moved for the latest update. It is by a black screw next to ATHR button. Also covered here: https://youtu.be/N4cxNccH66U?t=1412
    • Simbrief Import: On the EFB please confirm you are using your Simbrief Username (Letters and numbers), and not your PilotID (Numbers only)? 
    • DHL Livery Problems: Please share screenshots of the problem you notice

    Thanks!

  9. Hi, the KJFK is already optimized as much as it can be for Xbox. Are you noticing this issue on other airplanes like the default a320 as well? 

  10. 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!

  11. 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. 

×
×
  • Create New...