No replies to this topic

[dinodino]

Been some time since I refreshed my DOFLinx install, and when attempting the jump from 7.40 to 10.01 I've run into the following issue:

 

I have the 32-bit DOF installed in D:\DirectOutput

I have the 64-bit DOF installed in D:\DirectOutput64

 

My DOFLinx 7.40 install was in the D:\DirectOutput folder, but I wanted to follow the current standard of having it in a separate folder, so I removed all the DOFLinx files from D:\DirectOutput and created the D:\DOFLinx folder for a "fresh" install of DOFLinx 10.01

 

I've updated the included "DOFLinx - Shortcut" to point to the proper path, parameter location, and working directories on D:

I have updated all lines in the D:\DOFLinx\config\DOFLinx.INI file, and I have the following lines at the top:

DIRECTOUTPUTCONFIG=D:\DirectOutput64\directoutputconfig.ini

DIRECTOUTPUTGLOBAL=D:\DirectOutput64\config\GlobalConfig_B2SServer.xml

 

However, whenever I run the shortcut to try to start DOFLinx, I get a pop-up ".NET Unhandled exception" stating it could not load the file or assembly [file]D:\DirectOutput\DirectOutput.dll"

When I look in the DOFLinx.log file, I see "DOF path taken from old style fixed folder search = D:\DirectOutput\"

 

So, even though I have the paths in the INI set to point to the 64-bit DirectOutput folder, it is using the 32-bit folder which causes a bit-depth mismatch and crashes.

 

(BTW, If I rename D:\DirectOutput to D:\DirectOutputTest, DOFLinx properly pulls from D:\DirectOutput64, starts without errors, and works fine)

 

Am I missing something to get DOFLinx looking in the right place and not resort to an "old style fixed folder search"?

Any help GREATLY appreciated!... I've been banging my head against the cabinet for a while on this one and getting nowhere.

 

Regards,

Dino

Edited by dinodino, Yesterday, 06:00 PM.