I've used updater to install new sceneries without issues.
I've decided to start installing them on a larger external HDD, not my local (c:) HDD.
This has worked and I'm able to run sceneries from my E: with no issues - except for SOME sceneries.
If I tell Updater to move it to C:, it does and then the scenery works. If I move it back to E:, it fails to work. The test case I'm working with is Cascade scenery. I have included a screenshot of what condor sees as installed, versus contents of local c: drive and external e: drive.
I am stumped at this point and would appreciate any ideas. I tried creating a shortcut for Cascade in the C: scenery folder but that did not work so there must be something else I'm missing. I did remove the download files and force it to fetch a new copy while testing to rule out any issues with a previous download.
Thanks,
JW
Some sceneries do not work on external Hard Disk Drive
Some sceneries do not work on external Hard Disk Drive
You do not have the required permissions to view the files attached to this post.
Re: Some sceneries do not work on external Hard Disk Drive
You just need to recreate a symbolic link between your external HD and the Condor2/Landscape folder.
Search for "create a symbolic link" in this forum to find how...
Search for "create a symbolic link" in this forum to find how...
Re: Some sceneries do not work on external Hard Disk Drive
I heard symbolic-link, and as a retired unix admin, I got excited
Actually it is a Junction Link to be accurate, I believe. A simple shortcut on earlier troubleshooting did not look right (and did not work). Including the syntax I used (and verified it works) for an example to follow in case others stumble across this. Thanks for the guidance.
Directory of C:\Condor2\Landscapes
08/03/2022 02:56 PM <DIR> .
07/27/2022 11:39 AM <DIR> ..
07/29/2022 07:02 AM <JUNCTION> Arizona2 [\??\E:\Condor2_Scenery\Arizona2]
07/29/2022 07:08 AM <JUNCTION> Auckland [\??\E:\Condor2_Scenery\Auckland]
07/29/2022 07:43 AM <JUNCTION> Everest2 [\??\E:\Condor2_Scenery\Everest2]
07/26/2022 06:47 AM <DIR> Slovenia2
0 File(s) 0 bytes
6 Dir(s) 100,414,578,688 bytes free
C:\Condor2\Landscapes>mklink /J "Cascade Range" e:\condor2_scenery\"Cascade Range"
Junction created for Cascade Range <<===>> e:\condor2_scenery\Cascade Range
C:\Condor2\Landscapes>dir
Volume in drive C has no label.
Volume Serial Number is 2CAC-579B
Directory of C:\Condor2\Landscapes
08/04/2022 07:03 AM <DIR> .
07/27/2022 11:39 AM <DIR> ..
07/29/2022 07:02 AM <JUNCTION> Arizona2 [\??\E:\Condor2_Scenery\Arizona2]
07/29/2022 07:08 AM <JUNCTION> Auckland [\??\E:\Condor2_Scenery\Auckland]
08/04/2022 07:03 AM <JUNCTION> Cascade Range [e:\condor2_scenery\Cascade Range]
07/29/2022 07:43 AM <JUNCTION> Everest2 [\??\E:\Condor2_Scenery\Everest2]
07/26/2022 06:47 AM <DIR> Slovenia2
0 File(s) 0 bytes
7 Dir(s) 100,415,082,496 bytes free
Actually it is a Junction Link to be accurate, I believe. A simple shortcut on earlier troubleshooting did not look right (and did not work). Including the syntax I used (and verified it works) for an example to follow in case others stumble across this. Thanks for the guidance.
Directory of C:\Condor2\Landscapes
08/03/2022 02:56 PM <DIR> .
07/27/2022 11:39 AM <DIR> ..
07/29/2022 07:02 AM <JUNCTION> Arizona2 [\??\E:\Condor2_Scenery\Arizona2]
07/29/2022 07:08 AM <JUNCTION> Auckland [\??\E:\Condor2_Scenery\Auckland]
07/29/2022 07:43 AM <JUNCTION> Everest2 [\??\E:\Condor2_Scenery\Everest2]
07/26/2022 06:47 AM <DIR> Slovenia2
0 File(s) 0 bytes
6 Dir(s) 100,414,578,688 bytes free
C:\Condor2\Landscapes>mklink /J "Cascade Range" e:\condor2_scenery\"Cascade Range"
Junction created for Cascade Range <<===>> e:\condor2_scenery\Cascade Range
C:\Condor2\Landscapes>dir
Volume in drive C has no label.
Volume Serial Number is 2CAC-579B
Directory of C:\Condor2\Landscapes
08/04/2022 07:03 AM <DIR> .
07/27/2022 11:39 AM <DIR> ..
07/29/2022 07:02 AM <JUNCTION> Arizona2 [\??\E:\Condor2_Scenery\Arizona2]
07/29/2022 07:08 AM <JUNCTION> Auckland [\??\E:\Condor2_Scenery\Auckland]
08/04/2022 07:03 AM <JUNCTION> Cascade Range [e:\condor2_scenery\Cascade Range]
07/29/2022 07:43 AM <JUNCTION> Everest2 [\??\E:\Condor2_Scenery\Everest2]
07/26/2022 06:47 AM <DIR> Slovenia2
0 File(s) 0 bytes
7 Dir(s) 100,415,082,496 bytes free
Re: Some sceneries do not work on external Hard Disk Drive
CondorUpdater creates junctions automatically if you configure it to install landscapes in an alternate folder.
As you are a retired unix admin, you are probably more than comfortable with command prompt windows , but you could also use the small app I have written (CoJuGe, available on my tools page in the signature) that creates all missing junctions between the Condor landscapes folder and any alternate folder
As you are a retired unix admin, you are probably more than comfortable with command prompt windows , but you could also use the small app I have written (CoJuGe, available on my tools page in the signature) that creates all missing junctions between the Condor landscapes folder and any alternate folder
CN: MPT — CondorUTill webpage: https://condorutill.fr/