Jump to content

Crispy136

First Class Members
  • Posts

    241
  • Joined

  • Days Won

    6

Crispy136 last won the day on August 15 2023

Crispy136 had the most liked content!

Personal Information

  • Location
    Brisbane, Australia

Simulators

  • Sims Used
    MSFS

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Crispy136's Achievements

Community Expert

Community Expert (6/7)

  • Well Followed Rare
  • Dedicated Rare
  • Collaborator Rare
  • Conversation Starter Rare
  • First Post Rare

Recent Badges

72

Reputation

  1. I don't want users who follow my work to have to decide if they should ignore a dangerous download warning. PC security is there for a reason and ignoring defeats the purpose of having it. Either you turn it off altogether or you take notice of its messages. I've taken Nels comments onboard and have found a solution that solves the problem for my uploads. https://www.flightsim.com/profile/269250-crispy136/content/?type=downloads_file
  2. I don't know why it is for me to find a solution, as it only happens on Flightsim.com? Flightsim.com is not my responsibility. The exact same files downloaded on the same PC from another site using the same browser are not reported as malicious, ever. If it was something I am doing then it would happen on other sites for the same files, or even for other sites for different files, but it does not. Other people also experience the problem, so it is not an isolated event happening to one person. And it just happened again. Files that successfully downloaded an hour ago now are reported as unsafe. It's a real puzzle. And here is the comment I mentioned about Amazon servers. Sorry that I credited this to you when it was Adrian.
  3. I occasionally get nil file errors after I upload to Flightsim.com, so I always do a test download for any new livery to make sure the upload is valid. When I uploaded the livery below yesterday, I downloaded it straight away and the livery was blocked as unsafe. Hence my comment above. When I tried the exact same livery today it downloaded it without error. I use Chrome on WIndows 11, so it may be that one of those 2 is somehow the cause. Chrome config is set to block unsafe downloads, and that is not something I would ever turn off. But not sure if Chrome relies on WIndows 11 to tell it that a download is unsafe, so either could be the culprit. It's not related to only new files, as when I initially encountered the error I also tried a number of new and old downloads, both mine and from other authors, and all MSFS files were blocked. But FSX files downloaded without error at the same time MSFS files were being blocked. So it may be there is something in the structure that is triggering this error. I also upload the the same files to another site and only encounter this problem with Flightsim.com. You mentioned in another post that Flightsim.com file are stored on Amazon AWS servers. Could it be that there be some disassociation between those servers and whatever Chrome or Windows uses to identify an unsafe download? Then Amazon runs an update and all is working again?
  4. Yep, its back. Although it did disappear for a while. The exact same files continue to download successfully from other sites, so this problem can only be cause by this site.
  5. Looks like this problem has been resolved as MSFS downloads from Flightsim.com no longer trigger an "Unsafe download" warning.
  6. This only started on Chrome a few days ago. Doesn't happen when the exact same file is downloaded from other sites, so this is a Flightsim.com only issue. Seems to be limited to MSFS files as all the FSX files I tried all downloaded without error, while all MSFS files were blocked. Unfortunately Chrome doesn't appear to have an easy way to allow the download if it is blocked and there is no option to change it for just that download. In my opinion any advice to ignore downloads blocked by your browser is bad advice. While MSFS files happen to be harmless, many users will not have the technical expertise to make that decision. And who is to say if Flightsim.com hasn't been hacked and some malicious code has been added to the download. I am not willing to take that risk, so I don't expect people who download my liveries to do that either. As a result I pausing all uploads to Flightsim.com until the issue has been resolved. As this is only a problem with MSFS files uploaded to Flightsim.com, it would seem that Flightsim.com need to resolve the issue.
  7. Thank you very much Crispy!

     

  8. Crispy, please ass MSFS 2020 at the beginning of your repaint titles. It will distinguish which version of FS they are intended for and will also help with searching for them. With the new format of FlightSim, you can also rename the ones you have already uploaded. Thx.

    1. Crispy136

      Crispy136

      Ok I'll add MSFS to the name.  I don't want to use MSFS 2020 as it will obscure too much of the file name.  Perhaps you should direct this comment to the Flightsim.com themseves.  As all uploads have already been categorised into the various platforms by the uploader.  So that information is available but just not shown on some pages.

    2. PhrogPhlyer

      PhrogPhlyer

      Looks good, and I thing that will help people find your great repaints. The issue of file searches is an ongoing matter with the site. Hopefully they will improve that part. For now, I thing that we content creators have to struggle to ensure the members can find our works. I learn a little each time I review other peoples repaints, trying to improve mine. Thx.

  9. I treasure your work on this! Following you at flightsim.com! My pic of the Original Demo 150 Jet

    Regards

    Tom

     

    DSCF3221.JPG

    1. Crispy136

      Crispy136

      Rememeber that one well.  The Canadian F18 was one of my most difficult liveries.

  10. Love flying the A319. But it might be an idea to remove 2.7GB (uncompressed) of duplicate textures titled "original textures" from the upload. They are not used by MSFS and take up nearly half of the download. Just removing these drops the download file size down from 1.4GB to 800MB.
  11. duffys_tavern, you can get version .63 of the FBW by getting it from the github at https://github.com/flybywiresim/a32nx. Then click on word "Releases" on the right side of the page. Then scroll down until you get to version 0.63. Then click on v0.6.3. The scroll to the bottom of the page and click on "A32NX-stable.zip" to downlaod version 0.6.3. Note - FBW label all their downlaod versions with the same name, so I just rname them to add the version so I know what I've got.
  12. Great job! It is great to have some older generation jets and the A318 works well in MSFS. Would be better if the downloads weren't so large as these large files take so long to download. Just having a single livery in the main file would chop 25%u0025 off the A318 download. If there are any updates, people will have to download liveries they already have just to get an update of the core content. Can't comment on the A319 since it'll be another 3 hours until the download is finished! Other liveries could be available for download separately only if wanted. 10 of the 13 included A318 liveries appear with no thumbnail. Glad you are trying to fix the exhaust issue. None of these issues matter much, so thanks for sharing your work.
×
×
  • Create New...