Jump to content

Recommended Posts

Posted

@GregP I'm very glad you find it useful, thanks a bunch for your kind feedback!

1. I am planning to add a way to delete skins, but in the meantime you can double-click a thumbnail to open an explorer window. If you delete the folder, the UI will update to reflect that. I really should create a video explaining the various functionality I've implemented.

2. There are a few liveries that we can't install, especially those that contain a PDF or other instructions to go and download from elsewhere. I'll never understand why people compress an already compressed file, but if it's just a zip within a zip, I suppose that could be handled seamlessly. I'll take a look at one of his liveries and get back to you.

  • Like 1
Posted

Thanks for looking into it. And just to clarify, even if I unzip the outer zip, and then point LL at the actual zip with the skins, it gives me above error, so I'm thinking it must be something about the way he's describing his skins in the Lua file.

  • Like 1
Posted

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.

  • Like 1
Posted (edited)

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.

Edited by Camble
  • Like 1
Posted

Wow, thanks for the quick work!!!  I just tried the new version and verified that it does indeed work to install his skins.  Shame about missing the thumbnail though, but I look forward to you tackling that one too at some point.  😀

  • 2 weeks later...
Posted

not sure what im doing wrong but when i point the directories to locations on my pc it fails to see any liveries. Is there a discord to seek help?

Posted

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

  • Like 1
Posted

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.

 

  • Like 2
Posted

Excellent!! Perhaps you read my mind because just last night I was wondering if there was a way to manually do it already, and I meant to start poking around the files but then got distracted with other DCS tweaking. But this ability would be huge and I for one would be extremely appreciative of it.

  • Thanks 1
Posted

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.

  • Like 1
Posted

I've re-uploaded v0.23.0 - anyone who was already on this version should redownload and at least replace the updater.

  • Like 2
Posted

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.

  • Like 2
  • 4 weeks later...
  • 3 weeks later...
  • Camble changed the title to Livery Link - Install & Share Custom Liveries
  • 2 weeks later...
Posted

getting an error when launching it..

18:01:27 INFO] Configuring services
[18:01:27 INFO] Loading config
[18:01:27 INFO] Starting Livery Link v0.25.10
[18:01:27 EROR] One or more errors occurred. (Value cannot be null. (Parameter 'path1'))

 

Posted
13 hours ago, unclesneep said:

getting an error when launching it..

18:01:27 INFO] Configuring services
[18:01:27 INFO] Loading config
[18:01:27 INFO] Starting Livery Link v0.25.10
[18:01:27 EROR] One or more errors occurred. (Value cannot be null. (Parameter 'path1'))

 

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

Posted (edited)

"Value cannot be null. (Parameter 'path1')" error on first run has been fixed in v0.25.11

Sorry about that

Edited by Camble
Posted

Hi there,

I am interested in trying this software, but somehow I am not able to install it correctly. Starting the software I get this message: "DCS World" Installation folder not found, and asking "Please browse to your "DCS World" Installation folder". If I then click on OK, nothing happens. No Browse window opens.

So, how do I go about finding a solution for this? Any help would be appreciated.

Best regards and thanks in advance.

  • Thanks 1
Posted (edited)
10 hours ago, Camble said:

Hi @Aufpassen,

This issue has been fixed in v0.25.16, thanks for bring it to my attention!

TY! I'll try right away and will let you know how it goes.

 

Edit: Great utility and now works flawlessly.Again thank you very much!

😀

Edited by Aufpassen
  • Thanks 1
  • 4 weeks later...
Posted

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.

Livery Link v0.26.9.png

Posted (edited)

Just a heads up, BitDefender does not like your app and gives me this message: "Detection name: Gen:Variant.Tedy.769275"

I downloaded the zip and extracted it to a folder, and immediately my AV was tripped and it detected dozens of registry issues and the above Tedy virus.  Scanning the zip file led it to quarantine the main exe, but not the update.  

Either your file is compromised, or you're not being honest with your submission.  If you're on the level, I hope you can get this cleaned up and fixed for everyone else's sake.

Screenshot 2025-05-11 150940.jpg

Edited by Beerman2112
  • Thanks 1
Posted (edited)

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

Edited by Camble
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...