Jump to content

Camble

Members
  • Posts

    99
  • Joined

  • Last visited

Everything posted by Camble

  1. Latest release: v0.27.0 This version of Livery Link will now check inside nested archives for liveries. This is useful since some livery authors place several Zip/7zip/Rar files inside a single archive. This option is enabled by default, and can be disabled from the Tools menu. Livery Link will only ever extract valid texture files and description.lua files! https://github.com/Camble/LiveryLink/releases/tag/v0.27.0
  2. Valid point. Since people will have to disable for an entire environment, the protection is effectively lost since they can accidentally run a malicious mission if they allowed for another mission. Same goes for IC, something gets added to IC and the only workaround is to disable it completely.
  3. Is the allow list exhaustive? I know some server-side scripts that use "server" when calling dostring_in.
  4. @Czar66 lol keep 'em coming! Yes, stereoscopic mirrors for VR will be a performance hit, but it's achievable and VR users accept the trade-offs associated with VR. There is still an issue with the cockpit mirrors in 2D though, because they're just rendering to texture and don't account for the pilot's head movement. Implementing proper reflections for the cockpit mirrors won't really impact performance, and might actually improve it since the existing mirrors do impact framerate so much.
  5. Here's the latest update on how development for Livery Link Server is going: https://www.patreon.com/posts/livery-link-auto-129849245
  6. Found this, not sure if it works yet. https://wiki.hoggitworld.com/view/DCS_func_reloadUserScripts
  7. Looks cool! I'll need to give this a try.
  8. @Beerman2112 I can guarantee this is a false positive. I've confirmed your report by uploading the latest to VirusTotal and get the same detection. However, if we look at an older release, there is no detection flagged. This initially appeared to be due to the fact that the DCS mod was recently embedded. However, I've discovered it's something to do with how GitHub is publishing the builds. Anything I build locally is not flagged. I'm working on implementing a fix for this now, I'll post my findings in this thread as soon as I can. Thanks for letting me know. Update: This issue has been resolved in v0.26.10. Both the Livery link executable and the updater are both now self-signed, which seems to be necessary when using automatic builds like I now do. I've updated the User Files page and plan to automatically submit each new version to VirusTotal before release. This way, any new detections will be caught beforehand. Thanks again @Beerman2112 for bringing this to my attention. I only wish I'd noticed sooner.
  9. Bit of an update... I've been working on the server quite a bit lately, improving sharing and fixing minor bugs. v0.26.0 adds livery versioning, so when a livery author updates their User Files or Google Drive archive, Livery Link can tell. Usually Livery Link wouldn't re-download a shared livery if it's already installed, but now it will compare versions and re-download if the installed livery is out of date. I'll be adding a UI feature to manually check for updates soon. Added a fix for P-47 and Chinook liveries. Seems there are variants of these modules, which don't have their own folder, so had to make some adjustments for that. I'll monitor and add any more as needed, but the plan is to eliminate the need for manual maintenance at some point. Also refactored a bunch of older code. Doesn't change anything noticeable, but makes my life a whole lot easier and should improve stability. Any problems, please do reach out either on here or Discord. There's a channel for Livery Link and a few server hosts are trying out the pre-release server, so any feedback or bug reports only help make Livery Link better.
  10. Hi @Nate_p1, I think this is posted in the wrong forum. Here's the Livery Link thread, but feel free to contact me on Discord for some assistance.
  11. Hi @Aufpassen, This issue has been fixed in v0.25.16, thanks for bring it to my attention!
  12. "Value cannot be null. (Parameter 'path1')" error on first run has been fixed in v0.25.11 Sorry about that
  13. Seems to be an issue with first run on the later versions. Try this version https://github.com/Camble/LiveryLink/releases/tag/v0.25.6
  14. @janitha2 Thanks, the feedback is much appreciated! Glad you like it.
  15. v0.25.0 is out for both the server and client
  16. Decided to split the Google Drive integration into 2 phases. v0.24.0 includes phase 1, downloading and sharing public shares via Google Drive. Livery Link now lets you paste in a Google Drive link and, if you enable "Receive from untrusted download locations" in the options, you can receive shares from Google Drive as well. The second phase will include authentication, which will allow you to install privately shared liveries.
  17. I've re-uploaded v0.23.0 - anyone who was already on this version should redownload and at least replace the updater.
  18. Found a major issue in the updater for v0.23.0 - essentially once you update to this version, the updater fails to launch properly. I've temporarily removed this version until I can implement a fix.
  19. Something I'm working on for the next release, is the ability to change the thumbnail of a livery. This is especially useful for liveries installed from disk, where no screenshot has been scraped from user files.
  20. @WARcrime Hi, yes I've replied to you on Discord, but for future reference here... Livery Link won't (yet) pick up existing liveries. Install a livery either by pasting in a User Files URL, or from a local file on disk. You can also drag (compressed) files onto the app window to install liveries.
  21. The issue you were experiencing is fixed in v0.21.2. I haven't implemented extracting zips within zips yet. I'll probably look into this fairly soon, since installing from a local file misses out the thumbnail and Author details.
  22. Yea, I was able to reproduce the problem. As a workaround, it should be able to install if the texture files are inside a folder instead of at the root of the zip. I notice the readme for those liveries asks you to install them in CoreMods rather than User Files. I think it should work just fine, but worth pointing out. There may be a reason for that.
×
×
  • Create New...