Jump to content
Sign in to follow this  
Truckergogo

Live camera query Opus 5/P4

Recommended Posts

HI, hope you are all keeping cool in this heatwave :gaul:

Very impressed with Opus in P4, even without the PDK it works so well, just have one small problem...

How do I add an aircraft to the simobjects log, so that I can create and assign cameras to the aircraft? My Lancair and A2A 172 are both located outside the sim and arent in the list of aircraft within Opus. Ive tried to copy paste the location of the aircraft cfg files to the simobjects log but that isnt working for me.

Apart form that, Opus is working perfectly in P4, especially the LWA map on my second monitor, for me one of the best feature rich parts of Opus, indispensable once you start using it :)

 

Dave

Share this post


Link to post
Share on other sites

Having the same problem here, no aircraft in the P3DV4 Add-ons folder are recognized as an assignable aircraft by Opus 5 camera views.
The best you can do is assign to "All Aircraft".
Really hope there is a solution to this.

gb.


YSSY. Win 10, 6700K@4.8, Corsair H115i Cooler, RTX 4070Ti, 32GB G.Skill Trident Z F4-3200, Samsung 960 EVO M.2 256GB, ASUS Maximus VIII Ranger, Corsair HX850i 850W, Thermaltake Core X31 Case, Samsung 4K 65" TV.

Share this post


Link to post
Share on other sites

gb, ive figured it out.........

theres a file in your main Opus folder called   OpusFSI-Simobjects-Template.txt

The instructions are in the template, but basically you just copy the template, rename the copy to OpusFSI-SimObjects-P3D.txt, and add the location of the simobject folder or folders you want Opus to include, and paste it back into the main Fsi folder.

Mine looks like this, and now my A2a 172 shows up in the available aircraft for assigning cameras, so seems to work perfectly :). i just added the bit at the end, and changed the file name.

 

;-----------------------------------------------------------------
;                 OpusFSI SimObject Path Additions
;
; This file can be used to define a list of SimObject paths not
; currently identified by OpusFSI, normally addon aircraft that
; have been installed elsewhere and not defined anywhere that
; OpusFSI checks.
;
; Copy and rename the supplied OpusFSI_SimObjects_Template.txt
; file. Rename the file as indicated below. OpusFSI will check
; and process the following sim typed files for the additional
; path specifications,
;
; OpusFSI_SimObjects_FSX.txt
; OpusFSI_SimObjects_FSXSE.txt
; OpusFSI_SimObjects_P3D.txt
;
; For backwards compatibility, the file OpusFSI_SimObjects.txt
; is also checked for 'FSX Steam' sim types.
;
; N.B.
;
; Prepar3D systems should already include a 'simobjects.cfg'
; file within their common application data (c:\ProgramData)
; folder. These files are also checked and decoded by OpusFSI
; so try not to duplicated additional simobject paths in the
; above text file if used.
;
; Your specified SimObjects folders should each contain the
; same Airplanes or Rotorcraft sub-folders as the standard
; SimObjects folder within the sim.
;
; Don't forget to check that any addon folders are shared with
; adequate sharing and security permissions.
;-----------------------------------------------------------------

;-----------------------------------------------------------------
; Enter a list of SimObject paths not identified by OpusFSI.
;
; Each path must be entered on a separate line in the form,
;
; Path = <full_path_specification>
;
; For example,
;
; Path = E:\3rd Party\Company_XYZ\SimObjects
;-----------------------------------------------------------------

Path = C:\Users\David\Documents\Prepar3D v4 Add-ons\A2A\SimObject

 

Dave

 

 

Share this post


Link to post
Share on other sites

I am having the same issues as well. I will try this, thank you very much Dave. 

I am really dumb when it comes to these things.

fly safe


Francisco Blas
Windows11 Pro ASUS Hero Z790 | Intel i9-13900K | G.SKILL 32GB DDR5 | ASUS STRIX 4090 | WD 4TB SN850X NVMe | ASUS Ryujin II AIO 360mm | Corsair AX1600i | Lian Li 011D EVO | DELL Alienware 38 G-SYNC

Share this post


Link to post
Share on other sites
10 hours ago, Truckergogo said:

gb, ive figured it out.........

theres a file in your main Opus folder called   OpusFSI-Simobjects-Template.txt

Good detective work there Dave, thanks.
Hopefully Opus will add the Addon folder to it's standard look-up list in future.

gb.


YSSY. Win 10, 6700K@4.8, Corsair H115i Cooler, RTX 4070Ti, 32GB G.Skill Trident Z F4-3200, Samsung 960 EVO M.2 256GB, ASUS Maximus VIII Ranger, Corsair HX850i 850W, Thermaltake Core X31 Case, Samsung 4K 65" TV.

Share this post


Link to post
Share on other sites

I knew there had to be something in the FSI folder, and it all seems to be working ok, ive now added both of my aircraft that are outside the sim, and they can now be assigned camera views :)

And yes, it would be nice if Opus did this automatically, especially with P4 wanting third parties to install outside the sim.

; For example,
;
; Path = E:\3rd Party\Company_XYZ\SimObjects
;-----------------------------------------------------------------

Path = C:\Users\David\Documents\Prepar3D v4 Add-ons\A2A\SimObjects
Path = D:\lancair\SimObjects

 

Dave

 

  • Upvote 1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
×
×
  • Create New...