« previous next »
Pages: [1]

Author Topic: Vancouver problem or ORBX?  (Read 5194 times)

JFMITCH1716

  • Newbie
  • *
  • Posts: 30
  • stroke survivor/short term memory loss/impatient
Vancouver problem or ORBX?
« on: November 10, 2017, 04:55:48 pm »
Is this your problem  or ORBX?
Logged
Microsoft Windows 10 Home (64bit) 3x32" screens
32 GB RAM
12th Gen Intel (R) Core (TM) i9-12900K
Micro-Star International PRO Z690-A DDR4 (MS-025)
NVIDIA GeForce GTX TITAN X

Dave_YVR

  • Beta tester
  • Hero Member
  • *****
  • Posts: 803
Re: Vancouver problem or ORBX?
« Reply #1 on: November 10, 2017, 06:45:45 pm »
 I would think that is your problem as FSDT and ORBX PNW, LC and Vector work well together. Check your library insertion points.
Logged

JFMITCH1716

  • Newbie
  • *
  • Posts: 30
  • stroke survivor/short term memory loss/impatient
Re: Vancouver problem or ORBX?
« Reply #2 on: December 05, 2017, 09:23:44 pm »
Well I don't have ORBX Pacific NW but do have ORBX North America.  FSDT Vancouver occupies insertion point 1 although it works in other points as well.
« Last Edit: December 05, 2017, 09:51:20 pm by JFMITCH1716 »
Logged
Microsoft Windows 10 Home (64bit) 3x32" screens
32 GB RAM
12th Gen Intel (R) Core (TM) i9-12900K
Micro-Star International PRO Z690-A DDR4 (MS-025)
NVIDIA GeForce GTX TITAN X

peter w

  • Newbie
  • *
  • Posts: 33
Re: Vancouver problem or ORBX?
« Reply #3 on: August 16, 2019, 01:49:40 pm »
hi,
I do not know if it's still needed, but I had the same issue. i also use only orbx na lc, and vector, and as a solution i moved yvr below the first vector entry.
regards peter
Logged
Pages: [1]
« previous next »