Lightwright 6 Data Exchange issues

[mysecretstache]

I have a VWX file & Lightwright file linked via the XML file for data exchange, but as I make edits in LW, I get an alert "Cannot create Dudley's LP v2017.xml Data Exchange has been turned off"  This happens even if I start a new LW file with the same data.  I'm almost at the point where I can turn data exchange off, but ... it is a rather large inconvenience.  

This was a VWX file that started in v2016 and was updated to v2017 after the scenic updates started getting pushed to me in v2017.

I'm also crossposting this in the Lightweight forum to see if anyone bites there.

Thanks,
Simon

[Mickey]

Any chance you're using project sharing?

If so LW data exchange will not work.

 

[mysecretstache]

No project sharing.

[Hobbsies]

have you tried just deleting the .xml file and resyncing LW/VWX?

 

EDIT: If you're on dropbox or other file sharing service, I'd recommend saving all files to a local drive (your desktop) and re-trying.

Edited October 3, 2016 by Will Dean

[mysecretstache]

It could be a google drive thing.  I'm the only one working on these files, but I do keep my active projects on Google Drive  I'll Give it a shot.

 

[mysecretstache]

I have tried deleting the XML file a few times

 

[bshev]

I'm still on LW 5 and getting the exact same problem.  Every time I leave VW (not quitting, just changing active app or toggling to LW) the "perform complete export on exit" button in spotlight prefs unchecks itself.

 

Was also using google drive... saved locally and they seem to be syncing consistently now.

[klinzey]

In Spotlight the "perform complete export on exit" will automatically uncheck itself every time. "On Exit" is NOT exiting the Vectorworks application, it is on exit of the preference dialog.

The option should not remain checked, it is a one time option within the dialog.

"perform complete export on exit" will automatically be selected if the data exchange is turned on and there is no xml file present.

[Nik]

 LW requires continuos live access to the xml file. The small pauses of accessibility that are inevitable with any cloud based drive interrupts LW writing to the xml and then LW panics. Your best bet is to keep the xml file on your local drive. 

Edited October 7, 2016 by Nik

[ttidswell]

What Nik says, the software can't handle not having continuous access to the XML file. Try either pausing syncing to your cloud while working in LW/VW or save the XML in a file that only exists locally on your machine.