WHY are my plugin locations changed in my config?

[dmack]

I use all my plugins from a network drive (Z:). When I load up all my plugins from the Z: all is fine. I do NOT have autoscane plugins on. I close LW down, re-open and all is still fine but at some stage (possibly after a crash?) that I haven't figured out, I go back to add a plugin or something and find that all the plugin paths have been put back to the C:\. It's driving me crazy! What could I be doing wrong or is this a bug, if so, is it fixed in 9.3.1?

[mccabejc]

Same thing happened to me today when I was trying to setup network rendering. Drove me crazy. Wierd, huh?

[dmack]

Have you figured out what causes it? Is it after a layout crash that it get the configs again? I've thought of hiding the C:\ ones so it can't dot it - just under a bit of time pressure at the mo.

[BeeVee]

Yes, I have figured it out, and it's even written in the manual... ;) In Options in Layout (and in Modeler) turn off autoscan plug-ins.

B

[dmack]

Hi Ben,

So, could it be the autoscan in modeler messing it up in layout? The autoscan plugins is turned off in layout but I've just noticed it was on in modeler.....

[mccabejc]

Thanks BeeVee. I was going nuts trying to figure out why I'd changed my config file to a network mapped path, then after I started LW I'd find out that the file changed back to the C:\ path. Driving me nuts.

[ebouchoc]

Well...here's the issue. It's the HUB. If you don't want your configs to get screwed at any given time you must make them read only. For some strange reason the HUB will go bonkers and screw up everything from the Modeler configs to Layout configs to plugin configs. So, get your stuff all the way you want it then write protect them all. Turn off auto scan and any time you want to add something turn off write protect, add it and then turn it back on. All will be well.

[dmack]

Not convinced. I've got the hub permanently turned off and I got the issues. It might exacerbate the problem but it is not te lone culprit. I'm hoping that now I've turned off autoscan in modeler as well, all will be well, but I have a niggling feeling in the back of my mind it won't. It would be weird to have a global setting in TWO locations of the application. That in its own right would be daft.

[ebouchoc]

Yeah...I'm not entirely convinced either, however, write protecting the configs has worked wonders. How you can sold your issues.

[ebouchoc]

you know what...I just had a thought that you may want to try. I have a sneaking suspicion that if you open your HUB config file in a text editor you may just see the issue. Sometimes the old paths are still sitting there and if you delete the lines and then save you have the issue fixed. Just a thought.

[jaf]

As I read this thread it brings up some questions about the Hub. I don't have access to my LW machine to check this, but will later.

I have both 32 and 64 bit versions of 9.3.1 on my XP computer. I notice if I start Modelerx64 and then exit, the Hub stays running. What if I start Moderlerx32 (with the Hub initiated by Modelerx64?) Is it the same Hub? Is there a 64 bit version of the Hub? What about the beta Hub?

And what if your also running a beta version of Lightwave and you forget to exit the Hub and switch to the non-beta version of LW?

Anyway, I'm curious now and think I'll try a bit of experimenting. It seems to me that exiting Modeler without Layout running should cause the Hub to exit too.

[ebouchoc]

You know that's a good point. I believe that with the new HUB it holds all the versions that you open up and can switch between them right in the HUB interface in the tool tray. If you right click the HUB in the tool tray you should see all the versions, both 32 and 64 bit in there for you to launch from. The only thing is that this launch "station" if you will, will hold it all until you edit your HUB config file and remove the versions that you don't want. I have loaded 8.3, 9 and 9.2 and they are all in there, both 32 and 64.

Cheers:)

[jaf]

I used UltraCompare (part of the UltraEdit family) to check (compare) the three versions of Hub.exe (32 and 64 bit 9.3.1 and 1291 x64 beta) I have on my system and none compared. But a hex compare on exe's doesn't prove that the actual executable code is different. The compiler switches for x32 and x64, etc. will cause differences.

I guess a Newtek person probably has to answer this: Is it safe to mix x32 and x64 with the same version (in this case 9.3.1) Hub?

[BeeVee]

It's always best to turn off the hub between versions. It stops any Hub confusion which applications to link.

B