OP-X (and OP-X II) VST not retaining preset/patch settings in X3 Producer x64

I was wondering if anyone else had this issue. I've had OP-X and OP-X II (both 32bit VSTs) for a while. When I moved to X3, I made the leap from 32bit to x64 in Sonar. Now, I have other 32bit VSTs (like VB3) that I have no issue with, but for some reason, whenever I add one of these oberheim synths, any changes I make (whether it's picking a preset or twiddling a knob) isn't retained after a save/close.
 
I've tried this both in new projects and in existing projects from X2 that already had them added. I've gotten in the habit of making a manual save of any setting changes into a new bank and then referencing that bank name in the track name (so I can manually recall the sound between sessions), but it's a bit of a PITA.
 
Has anyone else encountered this issue?

ok - thanks. I did some searching and found that the "fix" was to modify some xml data in files inside Forte itself, not OP-X. I then did some digging in my VST directory and did things like verify full perms on the directory for my user. Also, running Sonar as admin (I don't usually) made no difference.
 
 

no worries - any little bit helps. I did some searching on SonicProject's website and came across some things related to Vista. I'm going to remove and reinstall the plugs tonight and set Sonar to run as admin full time (while the IT guy inside me cringes) and see if the behavior changes.
 
I'll also do some comparisons to VB3 (which also uses Jbridge, but seems to work) and see if I can correlate any differences. The way I understand it, both were written using synthedit, so I might be able to find something.

also if it's 32 bit it's the bitbridge process that needs admin rights?

lawp
also if it's 32 bit it's the bitbridge process that needs admin rights?

It's possible - although I'm not aware of anyone (on this forum at least) mentioning having to manually set the execution permissions on that. The way I understand how the "run as administrator" function operates in Windows is that when the root PID executes as administrator, all spawned child processes execute at that same permissions level.
 
Tonight I will run some tests to verify that the bitbridge processes are running with the proper privileges when I execute Sonar as administrator
(pasting this link for reference later)
http://www.sevenforums.co...istrator-elevated.html

I have both synths but am swamped at work and doing some long needed learning on X3/songwriting so haven't used either synth yet as they're still 32 bit.  However, you should let the company know as they've been pretty responsive to a couple emails I sent to them.... they're supposidly working hard on 64bit and I hope they improve the browser...
 
I've flagged this thread and will post thoughts as I have time.
 
best of luck, guys.
 

I heard back from SonicProjects and have been exchanging information. This is what he's theorizing:
 

This sounds to me as if it could have to do something with how the Sonar bridge handles fxp/fxb chunks. The prerset system of OP-X PRO-II is entirely fxp/fxb based. Most sequencers save the project with a complete fxb chunk (so the temporary version of a full fxb bank including all changes, with the last chose preset as default). It's possible than the Sonar bridge somehow handles this differently, maybe there's somewhere a setting for it.

 
He asked for some more data that I sent him, so I'm hoping that he may be able to come up with a fix (or at least a functional workaround).