Sorry about not including that info, I was mainly asking if it was a known issue.
The log files (included below) don't contain that much info though. They look pretty much identical in both cases.
The only difference is BitcoinP2P.cpp reporting connected to bitcoind in the db log file when it actually works.
I had a look at the code, and I think the problem could be in cppForSwig/BlockDataManagerConfig.cpp.
The btcPort_ variable is set to the #define value NODE_PORT_MAINNET rather than some kind of command line controlled variable. It is hard coded depending on main/test/regtest networks rather than allowing the port to be selected.
Standard PortBitcoind started (manually) with this line in bitcoin.conf. (default port used)
Armory started from command line with this.
C:\Program Files (x86)\Armory\ArmoryQt.exe --datadir=G:\armory_data --dbdir=G:\armory_data/database_dir --debug
It successfully connects.
dbLog.txt armorylog.txtAlternative Port (8500)Bitcoind started (manually) with this line in bitcoin.conf
Armory started from command line with this.
C:\Program Files (x86)\Armory\ArmoryQt.exe --datadir=G:\armory_data --dbdir=G:\armory_data/database_dir --debug --satoshi-port=8500
The GUI stays in offline mode.
dbLog.txt armorylog.txt