Addon Organizer Reporting Incorrect Paths

[Cruachan]

Hi Oliver,

Downloaded and installed from: addonorganizer_1_35_b01.zip

As you can see I have 2 violet entries. For the life of me I don't understand why this is happening. The paths have been checked and are okay. The Prepar3D v4.3  Scenery Library appears happy with both entries and they are active.

Ignore the red/pink entries - these addons (Scotflight, KMSP and MyTraffic) have been disabled temporarily.

Any ideas?

Thanks,

Regards,

Mike

[Lorby_SI]

Hello Mike,

the paths would be shown in violet if

- they are either invalid (=don't exist)

- or if they do not contain .bgl files

- or, in case of the (correct) referencing as a scenery area, if there is no subfolder called "scenery" that has .bgl files in it.

What is inside your folders? Maybe I am being to strict when I focus on BGLs?

Best regards 

[Cruachan]

Hi Oliver,

These images might help clarify what is causing this behaviour in the Addon Organizer:

:

5787 items

These files are inactive as I am using BLACK MARBLE NG VECTOR (FOR 3D BRIDGES) - much better than the ORBX offering 😀

Best regards,

Mike

 

[Lorby_SI]

Hello Mike,

so the app is actually doing what it is supposed to do. It can't differentiate between those folders being empty by accident or if you want them to be empty. 

Instead of renaming the BGLs you could have disabled the entry too, right? Maybe I should change the visuals, so that disabled entries always show in red, invalid or not?

Best regards

[Cruachan]

10 minutes ago, Lorby_SI said:

so the app is actually doing what it is supposed to do. It can't differentiate between those folders being empty by accident or if you want them to be empty. 

Instead of renaming the BGLs you could have disabled the entry too, right? Maybe I should change the visuals, so that disabled entries always show in red, invalid or not?

Best regards

Hi Oliver,

Not sure I understand you. None of what you see was done manually. There are no entries in the AFM\scenery folder at present as I had removed a single elevation correction made a few months ago using PILOT's AFM2 tool. However, the folder 'awaits' any further corrections I might make in the future.

FTX_VECTOR_OBJ\scenery

All the 'inactive' file extensions must have been placed there by FTXCentral as a consequence of my unchecking various entries in the FTX GLOBAL VECTOR Configuration Tool. This was part of the preparation before installing and using Black Marble Next Generation VECTOR.

Best regards,

Mike

[Lorby_SI]

2 hours ago, Cruachan said:

None of what you see was done manually.

Hello Mike,

that has nothing to do with it. P4AO can only detect that you (or an installer, scenery management app, whatever) linked a folder as scenery that does not contain a scenery. So it paints this entry violet. The program cannot know if you want it to be that way or if you accidentally linked an incorrect folder. 

The reason why empty folders are painted in violet is, that P3D V4.3 crashes in some instances while building the scenery index - if there are empty folders in the library.

Best regards

[Cruachan]

1 hour ago, Lorby_SI said:

Hello Mike,

that has nothing to do with it. P4AO can only detect that you (or an installer, scenery management app, whatever) linked a folder as scenery that does not contain a scenery. So it paints this entry violet. The program cannot know if you want it to be that way or if you accidentally linked an incorrect folder. 

The reason why empty folders are painted in violet is, that P3D V4.3 crashes in some instances while building the scenery index - if there are empty folders in the library.

Best regards

 

Hmm, that might explain the crash experienced this afternoon - involved in a troubleshoot involving FTXCentral with another developer - disabled his products entries in the Scenery Library while running in an active flight situation and the sim crashed as it started to rebuild the indexes. As I recall it was an api.dll error, I think, although can’t be certain as not at my PC right now so unable to check the Event Viewer. The same did not happen after reloading the sim and re-enabling those same entries. The indexes then rebuilt without further incident.

So, should I just ignore those two violet entries? I should perhaps say that I did not see any of this in a previous version of P4AO and I have been using it a lot to disable/enable/reprioritise entries.

Best regards,

Mike

[Lorby_SI]

2 minutes ago, Cruachan said:

 

Hmm, that might explain the crash experienced this afternoon - involved in a troubleshoot involving FTXCentral with another developer - disabled his products entries in the Scenery Library while running in an active flight situation and the sim crashed as it started to rebuild the indexes. As I recall it was an api.dll error, I think, although can’t be certain as not at my PC right now so unable to check the Event Viewer. The same did not happen after reloading the sim and re-enabling those same entries. The indexes rebuilt without incident.

So, should I just ignore those two violet entries? I should perhaps say that I did not see any of this in the previous version of P4AO and I have been using it a lot to disable/enable/reprioritise entries.

Best regards,

Mike

Hello Mike,

the violet entries are a new addition in the latest P4AO version. There is another thread in this forum where the issue with those crahes has been tracked down, and implementing the violet warning as a security measure was my attempt to help people out.

Personally, I would disable these entries. And this is where my initial thought comes in. Even if you disable it, it remains violet - and I don't like that. I will probably change it, so disabled entries are red, no matter if they exist or not. Haven't quite made up my mind yet.

Best regards

[Cruachan]

Thank you Oliver. Very useful info, I feel much wiser now!

Violet —> Red sounds like a plan. The Violet warns the user what is going on behind the scenes thus prompting the user to react appropriately by disabling the redundant entry before a crash ensues...... and wasted hours spent trying to pin down the cause.

Best regards,

Mike

[Lorby_SI]

Hello Mike,

the new version 1.35 b02 has been uploaded to the Lorby-SI website. Disabled entries will now show in red, no matter if they are valid or not.

Please note that this is also implemented for the "Other Addons", but that logic is only checking for non-existing paths.

Best regards

[Cruachan]

Hi Oliver,

Thanks for the heads up...downloading now!

Best regards,

Mike

[gaab]

Hello Oliver,

I was frightened today by your latest  release 🙂
I regularly check if every thing is ok on my system (I was about to update to 4.3) and... Orbx Object Flow entry was displayed in violet 😨

On 7/5/2018 at 7:32 AM, Lorby_SI said:

Hello Mike,

the paths would be shown in violet if

- they are either invalid (=don't exist)

- or if they do not contain .bgl files

- or, in case of the (correct) referencing as a scenery area, if there is no subfolder called "scenery" that has .bgl files in it.

 

I understand your checking logic but it is defeated in Other Addons by the will know Orbx ObjectFlow 2 entry.

No .bgl files here !  Ouf...

Best Regards,

Gérard

[Lorby_SI]

3 minutes ago, gaab said:

Hello Oliver,

I was frightened today by your latest  release 🙂
I regularly check if every thing is ok on my system (I was about to update to 4.3) and... Orbx Object Flow entry was displayed in violet 😨

I understand your checking logic but it is defeated in Other Addons by the will know Orbx ObjectFlow 2 entry.

No .bgl files here !  Ouf...

Best Regards,

Gérard

Hello Gèrard,

"Other addons" is not checking for BGL files - obviously. Something else must be wrong. "Other Addons" is only checked for non-existing/invalid paths, the contents of existing paths are irrelevant.

Best regards

[gaab]

 

Hello Oliver,

So, what's wrong here ? Prepar3D V4.2 does not complains...

Gérard

 

 

 

 

[Lorby_SI]

9 minutes ago, gaab said:

So, what's wrong here ? Prepar3D V4.2 does not complains...

Gérard

Hello Gérard,

this is a bug in P4AO. It expects a directory but it gets a file in the "Path" tag. I will correct this in the next version.

Best regards