Jump to content

Recommended Posts

Posted

Good morning,

I have an issue updating the aircraft in the iniManger. That happens not only with the A340 but also with the A350. Specifically when using SymLinks (e.g. with MSFS AddonsLinker).

How to reproduce the issue

  • Put the aircraft folder in your addon collection folder (e.g. mine is D:\2024\Addons\Aircraft\iniBuilds\A340)
  • Open MSFS AddonsLinker and activate the A340 -> a SymLink is created in your 2024 Community folder
  • Open the iniManager and update the A340

Expected Behavior

The aircraft updates successfully

Actual Behavior

The update fails as soon as files are being copied (so after the download) -> see attached screenshot

 

This issue has been present since the A350. I was patient, waited for fixes and updates to the iniManger (which happened a couple of times in the last months), yet this bug is still present.

Is there a known issue when using SymLinks? I mean, it works with every single other aircraft when doing updates, except for iniBuilds aircraft. Might as well happen with iniBuilds Scenery but I can't confirm it.

 

Cheers.

 

2026-02-02 09_45_31-iniManager.png

__________________________________________
image.thumb.png.ae77afbbb7f3d07a20e669fb2844c7a7.png
📺 YouTube: DroneSim
Posted
9 hours ago, DroneSim said:

Is there a known issue when using SymLinks? I mean, it works with every single other aircraft when doing updates, except for iniBuilds aircraft. Might as well happen with iniBuilds Scenery but I can't confirm it.

There shouldn't be. I use the linker and cannot reproduce this issue. Are you 100% sure you have defined the exact path in the manager client? 
There is a very small change the manager didn't save your predefined path so you may have to redefine it in the settings menu. 

explorer_7k0YdlYdAE.png

iniManager_UadEhNYD7j.png

explorer_cx41n5VelI.png

  • 3 weeks later...
Posted

Ok hold on, let me tell you what I did so far.

Created a folder D:\2024\Addons\iniBuilds

image.png.da87debf61cdd604f4a2c4796e45659c.png

Went into the Sim Paths in the iniManager and setup

a default path (via auto scan) where my community folder resides

image.png.c3413872f8cbd83df06d650c7a917505.png

a second path containing the stuff from iniBuilds

image.png.77f68dd56dcf0b09d550d3ad2d1720c4.png

 

Now if I install Wolf's Fang airport for example, I get to choose where to install it. I'll just select the second inibuilds folder. Now I have this

image.png.dee966f60c3df476411c5a05bbc6fe04.png

I like my stuff being ordered and well sorted. If I move the installed Wolfs Fang into the airports folder, the iniManager does not recognize it anymore as "installed". 

I think you can see my point here. It does not help to install all the stuff (aircraft, airports, liveries) into ONE single folder. What's the purpose of the SimPaths in the iniManager then if I put all my stuff into one folder? 

Next example (A340)

image.png.5aca8e4bd71393f31fae2706b4872399.png

Now, in order to see and update the aircraft in the iniManager, I would need to add the path above to my sim paths in the iniManager. That's fine if you have a couple of aircraft/liveries. But this also means that I need to add every single folder of every single aircraft as a custom path in the manager. Why? 

__________________________________________
image.thumb.png.ae77afbbb7f3d07a20e669fb2844c7a7.png
📺 YouTube: DroneSim

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...