Brilliant plugin.

 

Very difficult to see anything though, I can't seem to get any sort of AA going, which makes text completely illegible. Havne't gotten my flight stick plugged in so haven't tested the zoom in function.

 

Not even fussed about the screendoor effect, it's just the lack of AA that makes the jaggies so much harder to read.

 

I couldn't figure out how to supersample the DK2, which works for Elite Dangerous to improve sharpness - any suggestions anyone?

Ok done a bit more testing and I think there's room for improvement, not necessarily in the plugin but the way P3D is outputting, perhaps. Have a go of:

 

https://developer.oculusvr.com/forums/viewtopic.php?f=42&t=8423&start=20 for the minisim for DK1/DK2.

 

It certainly is possible for a bit more legibility in the gauges, but I'm not seeing this in my version of DK2 enabled P3D v2.4. Does it look like the minisim for anybody else? As I'm seeing a lot less antialiasing for P3D through DK2 so all lines are WAY more jaggier inside Prepar3d.

 

Edit: Okay, only way I managed to fix it was to use 4x SGSS through NVidia Inspector. That's cleared up the jaggies, and the gauges are somewhat readable, and with everything set to low there's not really any noticeable tearing. Text however, such as the GPS, is still too difficult to read. Not sure what else can be done, other than to wait for Oculus Rift CV1. Fantastic experience nonetheless.

The plugin works great, thank you!

The zoom function actually makes instruments readable.

 

One thing i noticed was that there seems to be no cockpit sounds like switches and warning horns. Without the plugin all audio works.

Anyone else with this problem?

I'm Using P3D 2.4 and have tried PMDG 737NGX and ES Citation X 2.0.

Hi all,

 

I'm currently having problems using the zoom and position controls on the joystick hat. In options I select which one I want the hat to control but back in the sim nothing happens.

 

Everything looks great in the DK2, I can scale the aircraft so immersion is good and head tracking and positioning is working fine. It is the only problem but it is a bit of a big one as most aircraft put you in the wrong position inside the aircraft.

 

I'm running it in 2.4 and have tried it with default scenery and aircraft with only my joystick and saitek pedals connected and have disabled fsuipcs so it is just the basic sim using the standard prepar3d control assignments. When I run on a monitor the hat works as it should and you can pan the view.

 

Any thoughts on why?

 

Regards

Chris

Hi,

 

I have an installation problem, apparently:

 

The plugin is not seem to be "added on". Should it be seen in the "Add-ons" menu inside p3d?

 

My configuration and checks:

Oculus dk2 working, version 0.4.2.

I set everything as required - switched the OR to be the main display.

Run everything as administrator.

 

P3D (v2.4) still starts in the wrong display, with no stereo view, with no DCOC seem to be running.

 

On a friends (stronger) PC - worked 100%, same configuration steps.

 

Differences:

I have fsuipc installed.

I have REX installed, as well as few scenery. 

I have a few older versions of P3D installed, but their folders under C:\Program Files (x86)\Lockheed Martin    - are renamed and not used. 

Active folder of P3D has default name - Prepar3D v2.

 

 

How do i check if DCOC was added correctly to the P3D as an add-on ?

 

Is there another way to run the DCOC, other that running the DCOCLauncher.exe ?

Is there a log file ?

 

Haven't tried yet - fresh reinstall the p3d.

 

Regards,

Israel

Hi guys

 

I removed my sidewinder and pedals and all other Saitek throttle quads and yoke. Plugged in just my Saitek fly 5 and tried again and it works so it must be just a conflict, I will recheck the control mappings. No idea why but obviously dcoc doesn't like all my controllers. With the single joystick I can move view position and zoom.

 

Thanks!

 

P.S. Israel,

Check your dll.xml file in this location (C:\Users\username\AppData\Roaming\Lockheed Martin\Prepar3D v2). Obviously where it says username is your actual username. Open it in notepad and see if it looks anything like this, you will see I have a few entries but currently fsuipc is disabled. It is the bottom entry that is important. If you don't have a dcoc entry then it didn't install correctly.

 

 

<?xml version="1.0" encoding="Windows-1252"?>
<SimBase.Document Type="Launch" version="1,0">
 <Descr>Launch</Descr>
 <Filename>dll.xml</Filename>
 <Disabled>False</Disabled>
 <Launch.ManualLoad>False</Launch.ManualLoad>
 <Launch.Addon>
  <Name>ObjectFlow</Name>
  <Disabled>False</Disabled>
  <ManualLoad>False</ManualLoad>
  <Path>D:\Prepar3D v2\ORBX\FTX_AU\FTXAA_ORBXLIBS\Scenery\ObjectFlow.dll</Path>
 </Launch.Addon>
 <Launch.Addon>
  <Name>FSUIPC 4</Name>
  <Disabled>True</Disabled>
  <Path>Modules\FSUIPC4.dll</Path>
 </Launch.Addon>
 <Launch.Addon>
  <Name>FSForce DLL</Name>
  <Disabled>false</Disabled>
  <ManualLoad>true</ManualLoad>
  <Path>C:\Program Files (x86)\FSForce 2\FSForce.dll</Path>
 </Launch.Addon>

 <Launch.Addon>
<Name>DCOC</Name>
<DLLType>PDK</DLLType>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>DCOC_02.dll</Path>
</Launch.Addon></SimBase.Document>
 

Awesome plug in!

Is there any way of letting DCOC know which joystick hat to use? As soon as I plug in pedals/yoke/quadrants the hat zoom and position stops working.

 

Regards

Chris

Hi!

Plug-in works. I believe this is huge step ahead for us simmers, toward the perfect realism.. I would certainly pay for software pieces like this.

 

Joystick hat still doesn't do anything here. Should I bind the hat to any axis inside p3d?

 

Where is the best place to get documentation and tips like those you put in the dcoc 1 page?

 

And where do people share their ideas and suggestions about dcoc?

 

Like this one : is their a way to have outside view (spot plane etc.)?

 

Israel

Hi Israel

Joystick hat only works if there is only one joystick device connected. Works fine for me if I unplug pedals and throttle etc and just have one joystick. That way you can adjust position etc.

 

Unfortunately for me, without the facility to tell DCOC which joystick hat to use its is unusable for me as I can't fly without pedals and throttle quadrant.

 

It is a stunning plug in though and only needs this adding to make it the perfect oculus solution.

 

Chris

I know this is an old thread now, but for anyone struggling to read gauges who has a GTX970 / 980, try using dynamic super resolution and bumping the res of the DK2 up to 4K. It completely transforms the gauges and makes them readable just by leaning forward - at least in a small cockpit like the C172.