[LDView] Command line call with INI file, no function

[Manfred Schaefer]

Hello,
I want to take snapshots with LDView. For this purpose, I have saved the required settings in an INI file. The ldr file, the INI file, and the LDView64.exe program are located in the same directory.
The call looks like this: LDView64.exe 157.ldr -IniFile=Settings.ini.
It seems as if the INI file is not being used. A BFC=0 entry in the INI file has no effect. For example, if the call looks like this, the result is as expected: LDView64.exe 157.ldr -BFC=0.
What am I doing wrong?
I am using LDView 4.5 and Windows 10.

Regards

Manfred

[Orion Pobursky]

What does the INI file contents look like? Do you have everything under the "[General]" header?

[Manfred Schaefer]

What does the INI file contents look like? Do you have everything under the "[General]" header?

The contents of the INI file are as follows:

[General]
Antialias=4
AutoCrop=0
BackgroundColor3=0xebebeb
BFC=0
Blckhighlights=0
BoundingBoxesOnly=0
ConditionalHighlights=1
CurveQuality=12
DrawLightDats=0
EdgeThickness=1
EdgesOnly=0
HiResPrimitives=1
Lighting=1
PerformSmoothing=1
PolygonOffset=1
SaveZoomToFit=0.95
SaveImageType=2
SaveWidth=800
SaveHeight=600
ShowAllType5=1
ShowHighlightLines=1
SubduedLighting=1
UseQualityLighting=1
UseSpecular=0
Wireframe=0

I also tried the following without success:
[Geometry]
BFC=0

[Travis Cobbs]

Hello,
I want to take snapshots with LDView. For this purpose, I have saved the required settings in an INI file. The ldr file, the INI file, and the LDView64.exe program are located in the same directory.
The call looks like this: LDView64.exe 157.ldr -IniFile=Settings.ini.

There is a bug that is causing it not to work with relative paths to the ini file. If you specify the full path to the file instead of just Settings.ini, it should fix the problem.

I created a GitHub issue: https://github.com/tcobbs/ldview/issues/91

[Manfred Schaefer]

There is a bug that is causing it not to work with relative paths to the ini file. If you specify the full path to the file instead of just Settings.ini, it should fix the problem.
I created a GitHub issue: https://github.com/tcobbs/ldview/issues/91

Thanks Travis, it works now.

Greetings

Manfred

[Manfred Schaefer]

Hello,
Now I have another problem.
I've created directories in LDView containing unofficial parts, and I've also written these directories to the INI file. When I display the unofficial part directly in LDView, it works. However, when I call it from the command line using the INI file, an error occurs.
LDView tries to access the Parts Tracker, but since there's no internet connection, it fails.
Here's the section from the INI file:

[ExtraSearchDirs]
D:\Teile_inoffiziell\Helper\Parts
D:\Teile_inoffiziell\Unofficial\Parts
D:\Teile_inoffiziell\Unofficial\p

Regards
Manfred

[Manfred Schaefer]

Hello,
Now I have another problem.
I've created directories in LDView containing unofficial parts, and I've also written these directories to the INI file. When I display the unofficial part directly in LDView, it works. However, when I call it from the command line using the INI file, an error occurs.
LDView tries to access the Parts Tracker, but since there's no internet connection, it fails.
Here's the section from the INI file:

[ExtraSearchDirs]
D:\Teile_inoffiziell\Helper\Parts
D:\Teile_inoffiziell\Unofficial\Parts
D:\Teile_inoffiziell\Unofficial\p

Regards
Manfred

I found the cause. I forgot the keyword. The entry should look like this:

[ExtraSearchDirs]
Dir001=D:\\Teile_inoffiziell\\Helper\\Parts
Dir002=D:\\Teile_inoffiziell\\Unofficial\\Parts
Dir003=D:\\Teile_inoffiziell\\Unofficial\\p

Regards
Manfred