HOME | ABOUT | FORUM | FILES | ARTICLES | MULTIPLAYER | FAQ | STORE | GALLERY
Terms of use • Privacy statement  
 


» Welcome Guest
[ Log In :: Register ]

 

[ Track this topic :: Email this topic :: Print this topic ]

Topic: Dodo p3d v3.4 + win10< Next Oldest | Next Newest >
JACN
(HC234JA)
Offline





Group: Member
Posts: 250
Joined: Feb. 2004
Posted: Dec. 18 2016,22:05

Hi,

I have recently updated from win7 to windows10 pro 64bit and also I have installed p3d v3.4.

When I have installed dodo 206 by copying rotorcraft folder, dll to gauge, effect file, etc.. the same way I did in win7 and p3d v3.3...I have found that it doesn't work.

Some switches are no longer working, the upper left corner light in the caution panel lights and I can't even start the engine.

Any idea? ...anyone managed to make dodo work in a similar setup?  Win10 +p3d  (v3.4)

Thanks in advance!

PS: we do need an updated version...this awesome helo sim is dying :(
Back to top
Profile PM 
JACN
(HC234JA)
Offline





Group: Member
Posts: 250
Joined: Feb. 2004
Posted: Dec. 19 2016,17:46

Fixed! :cool:

Cheers,

Álvaro
Back to top
Profile PM 
Simon853
(HC685SI)
Offline





Group: Member
Posts: 2291
Joined: Sep. 2005
Posted: Jan. 06 2017,12:26

Could you specify how you fixed the problem for others' benefit?

BTW - If nothing works but the top left annunciator light illuminates, it means that it is failing to open a SimConnect client.  This usually means that the legacy (FSX) SimConnect dlls are not being found within the WinSxS system directory.  LM provide installers for these with P3D.

Si
Back to top
Profile PM 
JACN
(HC234JA)
Offline





Group: Member
Posts: 250
Joined: Feb. 2004
Posted: Jan. 20 2017,20:51

Yes, sorry.

Fsx + acceleration installation solved the problem.

Cheers,

Álvaro

Ps: Dodo in VR is simply AWESOME... :cool:


Edited by JACN on Jan. 20 2017,20:51
Back to top
Profile PM 
Cirodi
(HC537CI)
Offline





Group: Member
Posts: 6
Joined: May 2017
Posted: June 14 2017,13:24

Quote (JACN @ Jan. 20 2017,20:51)
Yes, sorry.

Fsx + acceleration installation solved the problem.

Cheers,

Álvaro

Ps: Dodo in VR is simply AWESOME... :cool:

Hello,
what do you mean with "Fsx + acceleration installation solved the problem"?
Did you installed in parallel with Prepar3d v3?
Are you flying dodosim 206 with what?
Thanks.
Back to top
Profile PM 
JACN
(HC234JA)
Offline





Group: Member
Posts: 250
Joined: Feb. 2004
Posted: June 14 2017,16:31

Quote (Cirodi @ June 14 2017,13:24)
Quote (JACN @ Jan. 20 2017,20:51)
Yes, sorry.

Fsx + acceleration installation solved the problem.

Cheers,

Álvaro

Ps: Dodo in VR is simply AWESOME... :cool:

Hello,
what do you mean with "Fsx + acceleration installation solved the problem"?
Did you installed in parallel with Prepar3d v3?
Are you flying dodosim 206 with what?
Thanks.

Hi,

After a fresh Windows 10 installation + P3d v3, Dodo did not longer work. So, I decided to install FSX+ Acceleration...and worked again.

I guess the issue was solved when FSX installed old .NET versions and/or DX9/DX10 packages included in the installer as part of it. Those are not included in Windows 10 or the newer versions in Win10 are not fully compatible backwards.

After that I had Dodo working again and better than ever with VR (Flyinside).

Hope this helps,

Álvaro


Edited by JACN on June 14 2017,16:33
Back to top
Profile PM 
Simon853
(HC685SI)
Offline





Group: Member
Posts: 2291
Joined: Sep. 2005
Posted: June 14 2017,20:02

The Dodo relies upon the FSX SimConnect.dll. P3d does not install this by default. There's a legacy support installer somewhere in P3D or its SDK that installs it for you.  (Installing FSX+Acceleration/SP2 effectively does the same thing, but that's unnecessary overkill. )

Si
Back to top
Profile PM 
JACN
(HC234JA)
Offline





Group: Member
Posts: 250
Joined: Feb. 2004
Posted: June 14 2017,20:16

That explains all, thanks :;):

(Without that specific info I had to go the hard way...but worked!)

Álvaro
Back to top
Profile PM 
Cirodi
(HC537CI)
Offline





Group: Member
Posts: 6
Joined: May 2017
Posted: June 15 2017,09:58

Hi Mates!
You both are correct.
I replicated JACN installation and it worked, then I uninstalled FSX and ACC with and advanced tool so to keep FSX SimConnect.dll.
Everything works great.

Thank you both!
Back to top
Profile PM 
Cirodi
(HC537CI)
Offline





Group: Member
Posts: 6
Joined: May 2017
Posted: July 12 2017,20:08

Quote (Cirodi @ June 15 2017,09:58)
Hi Mates!
You both are correct.
I replicated JACN installation and it worked, then I uninstalled FSX and ACC with and advanced tool so to keep FSX SimConnect.dll.
Everything works great.

Thank you both!

To Simon

Any idea to make it working with P3D v4?
Back to top
Profile PM 
Simon853
(HC685SI)
Offline





Group: Member
Posts: 2291
Joined: Sep. 2005
Posted: July 15 2017,22:13

That's literally impossible because a 64 bit application cannot load a 32 bit dll. It's a fundamental Windows architecture issue.

Furure versions will though. I have our Pro version running under v4 but it's a majorly re-engineered code base and still undergoing a lot of enhancements and test.  This will eventually form the basis for both an FSX and P3D 32bit release and 64 bit, but it's a way off while the 3d model matures.

I might look at the amount of effort required to port the FSX version to 64 bit, but we never officially supported P3D for that product anyway.


Si


Edited by Simon853 on July 15 2017,22:14
Back to top
Profile PM 
kevinh
(HC667KE)
Offline





Group: Member
Posts: 2
Joined: Aug. 2017
Posted: Aug. 02 2017,10:02

Is it not possible to recompile the gauge code for 64 bit operation?

--------------
Kevin
Back to top
Profile PM 
Simon853
(HC685SI)
Offline





Group: Member
Posts: 2291
Joined: Sep. 2005
Posted: Aug. 04 2017,15:59

It's not as straighforward as that.  I converted the code-base I'm currently working on (which will be for the new HD version) and I had to do a lot of re-working of code on top of that.  The FSX version also does not load the SimConnect.dll in the conventional manner, where you specify the dependency in the dll manifest and then let the WinSxS subsystem load it.)  Instead I load it programmatically at runtime by searching it out and loading it through the Windows system call.  But this only works for the legacy SimConnect dlls because they're all 32 bit.  Native P3D assemblies statically link SimConnect at compile time.  (I did it that way because so many people were having trouble with their SimConnect installations after moving FSX to new drives, etc.)

I would have to re-write a lot more code to replace that mechanism.  Instead I'm concentrating my time on implementing new features into the new version which will support FSX, P3D 32 and 64 bit, since we stated at the outset when P3D was released that although the 206 FSX should work in P3D, we did not officially support it.  And if we did upgrade the FSX version to P3D 64 bit we'd have to put it through a lot of testing and the support we'd likely have to give to a whole new set of problems would derail the current development.

Hopefully sometime soon we can start showcasing some of the new features we've been working on when the 3D model has matured a little more.

Si
Back to top
Profile PM 
kevinh
(HC667KE)
Offline





Group: Member
Posts: 2
Joined: Aug. 2017
Posted: Aug. 07 2017,19:26

Thanks for taking the time to explain, Si. Much appreciated.

--------------
Kevin
Back to top
Profile PM 
13 replies since Dec. 18 2016,22:05 < Next Oldest | Next Newest >

[ Track this topic :: Email this topic :: Print this topic ]