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


» Welcome Guest
[ Log In :: Register ]

Pages: (3) < 1 [2] 3 >

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

Topic: Problem dodo heli for oculus rift< Next Oldest | Next Newest >
higgy_de
(HC722HI)
Offline





Group: Member
Posts: 26
Joined: Jan. 2017
Posted: Jan. 16 2017,16:20

Thanks, but i read and see vids where they fly dodosim in oculus rift ...so i think somehow ...it will go ( fly ) :)

--------------
regards, Higgy
Back to top
Profile PM 
Simon853
(HC685SI)
Offline





Group: Member
Posts: 2307
Joined: Sep. 2005
Posted: Jan. 16 2017,18:20

I know we have a few customers at least using it successfully, so tracking down your problem could be tricky.  Like I said, it often crashes for me, sometimes on a flight I saved the last time I landed.  There is no obvious reason.  I usually just try to create  new flights, or try loading first with a different aircraft and then swap to the 206 once it is running.

Hopefully we can find a cause befoew too long.

Si
Back to top
Profile PM 
higgy_de
(HC722HI)
Offline





Group: Member
Posts: 26
Joined: Jan. 2017
Posted: Jan. 19 2017,11:25

??

--------------
regards, Higgy
Back to top
Profile PM 
higgy_de
(HC722HI)
Offline





Group: Member
Posts: 26
Joined: Jan. 2017
Posted: Jan. 25 2017,12:03

hello ?

--------------
regards, Higgy
Back to top
Profile PM 
higgy_de
(HC722HI)
Offline





Group: Member
Posts: 26
Joined: Jan. 2017
Posted: Jan. 29 2017,10:09

i think this "dicussion" is dead ...
So dodosim dont work with fsx for steam


--------------
regards, Higgy
Back to top
Profile PM 
Manilow
(HC225MA)
Offline





Group: Student Pilot
Posts: 1122
Joined: Oct. 2005
Posted: Jan. 29 2017,11:07

I have to disagree.... It works with fsx steam problem is you are using an oculas with Flyinside I think. Problem is in your system somewhere.

Have you installed steam in your program files section ie (x86 Program files)?
I have my steam folder as C:/Steam and the UAC protection in Windows 10 lets me alter everything in my steam apps without interfering.

If you already have steam installed like this disregard...

Trying to help...

Andy


--------------
Andy Walker
Back to top
Profile PM MSN 
Rogue Trooper
(HC020RO)
Offline





Group: Student Pilot
Posts: 72
Joined: May 2007
Posted: Jan. 30 2017,09:51

Hi Higgy,

This is just my two cents and am not speaking on anyone's else behalf. I'd like you to know I have been using the dodo for several years now and I can't speak highly enough about it. It is the most realistic fsx  addon I've ever used and I simply can't bring myself to fly anything else.
I have had several issues with the very complex setup I am Using.(Hardware gauges, flight controls, warning lights and switch panels, multiple monitors etc).
Despite the fact that all of this hardware is nothing to do with the dodo, Simon and Mark have gone out of their way to find solutions for issues that they don't actually support. This includes finding new ways to make the dodo function with emergent hardware and software addons too.

I'm not sure if you moved from a boxed fsx to steam. If you did that can cause a mass of problems with addons not finding the steam edition. FSXINSIDER.com has a very good 2 part migration tutorial that might help. For best results both the boxed edition and steam should be removed and the registry cleaned before re installing steam. That sorted a lot of problems for me with crashes involving my video card and the various addons finding fsx.

I suggest you read some of the posts here to see how many satisfied customers are out there. From my observation the posts about the issues you are experiencing come across as rude and disrespectful. I'm sorry if I have misinterpreted your intent if that's not the case.

I hope you find a resolution to your problems.

Please remember that hovercontrol is a community of heli flight sim enthusiasts who are generally very happy to help as are the dodo team. From what I have seen Simon is going out of his way to find a solution for you. So maybe you could give him some slack!

Cheers,
Stuart
Back to top
Profile PM AOL 
higgy_de
(HC722HI)
Offline





Group: Member
Posts: 26
Joined: Jan. 2017
Posted: Jan. 30 2017,22:26

Thanks for reply ...
yes, my steam inside FSX with VR works with every addons i have, als with every other thing in FSX ...So i am wondering that the dodosim is not working.
( no i have not update / upgrade on this computer here, and the path is ok ....

I am a Pilot in real as well and i really go lucky when i can dodosim test and fly in VR ...thats why i am buy it 5 or 6 weeks ago and test and try everything ( my work is Network and Computer also since 20 years , so i am not a newbee ) :) I programmed 20 years ago for RC -Sim planes and helicopters for free and build hardware also and start a free community for this 18 years ago for nearly now 100.000 users.
Because of this I have no problem to pay for a good working heli (more as the sim costs :) ) , because everywhere I read they are happy with this addon and i know how much work this is.

But for "neveruse" its to much money to throw away ... :)
Hope you understand.

I just work on my Motion platform (3dof) and adding / build some hardware, so with the dodosim I want really to fly with this "real copter" in FSX what i read everywhere ( but never tested ) :(


Edited by higgy_de on Jan. 30 2017,22:34

--------------
regards, Higgy
Back to top
Profile PM 
Simon853
(HC685SI)
Offline





Group: Member
Posts: 2307
Joined: Sep. 2005
Posted: Jan. 30 2017,22:42

I am unable to reproduce this problem. Unless it stops working for me there's nothing I can suggest.  As you know, many people have got it to work with Steam FSX, FSX (CD), P3D in combination with the Oculus Rift.

You said it is working as expected in FSX Steam, so it is working as designed. Occasionally other add-ons appear that cause a conflict somehow and we do what we can to identify and resolve the issues if we can.  But in this instance it appears likely that the crash is being cause by something within the FSX core or Fly Inside, neither of which we can debug.

All four components, the 206, FSX, Fly Inside and the Oculus run-time itself rely heavily on operating system features, libraries, etc. Any one of these could be the root of the problem. The fact that Windows is reporting a Fatal Error without providing any further detail doesn't make tracking the problem down easy.

I'm continuing to try and think of ways in which we might be able to narrow it down.

Perhaps you could take a look in the Windows event log after a crash to see if provides any additional information, like the module that caused the crash?

Si
Back to top
Profile PM 
higgy_de
(HC722HI)
Offline





Group: Member
Posts: 26
Joined: Jan. 2017
Posted: Jan. 30 2017,23:56

Tell me what you need, i will send it, no problem ...

But i think all of the last days since your post here, i have to wait because you work on the error ?!?!

That you have not enough information to start the search for a sololution for the problem is new for me now . :(

So , i will help so much as i can, but you have to tell me what you need.


Edited by higgy_de on Jan. 30 2017,23:57

--------------
regards, Higgy
Back to top
Profile PM 
Simon853
(HC685SI)
Offline





Group: Member
Posts: 2307
Joined: Sep. 2005
Posted: Jan. 31 2017,12:48

There isn't any information I need.  My mention of the Windows Event Log was just a thought, but when FSX has crashed with FlyInside running in the past for me with similar errors, the event log has not contained any useful information.

Note that many people report that the 206 works ok for them with Steam FSX and FlyInside.  Tracking down unique problems like this can be virtually impossible where there's no debug information reported, but I continue to try and find a way.

Si
Back to top
Profile PM 
Simon853
(HC685SI)
Offline





Group: Member
Posts: 2307
Joined: Sep. 2005
Posted: Jan. 31 2017,19:15

Some "good" news:   It's crashed on me a couple of times this evening after more repeated testing.  Once it started doing it, it crashed repeatedly for a few more times, during which I was able to try a few ideas out.  So though I have no solution yet, I'm beginning to narrow the problem down.

Si
Back to top
Profile PM 
Simon853
(HC685SI)
Offline





Group: Member
Posts: 2307
Joined: Sep. 2005
Posted: Jan. 31 2017,21:56

Well, I've isolated the problem to a probably timing issue when FSX loads and initialises the aircraft's dll, connecting it to the window, etc.  This is more complicated than a default aircraft because the Dodo dll also opens an in-process SimConnect client and DirectSound instance.  FlyInside is also doing the same things, plus a lot of other Direct3D clever tricks.  

So, I'm making some progress in identifying when the problem is occurring, but none yet as to how to prevent it.

Si
Back to top
Profile PM 
higgy_de
(HC722HI)
Offline





Group: Member
Posts: 26
Joined: Jan. 2017
Posted: Feb. 01 2017,10:32

:D  will wait for it :)

--------------
regards, Higgy
Back to top
Profile PM 
Simon853
(HC685SI)
Offline





Group: Member
Posts: 2307
Joined: Sep. 2005
Posted: Feb. 03 2017,19:57

I have made some changes to the order of things that get initialised when the 206 loads (including when it is only selected in the Create Flight dialog, since that effectively loads and runs the .gau dll also.)

Initial tests seem to be good.  It's not crashed on me in about 20 reloads.  However, I need to do a lot of testing to verify that it has not inadvertently broken anything or introduced other unwanted behaviour.)

If the testing goes well, I will give you an updated .gau file to try.  Hopefully within the next couple of days.

Si

PS.  You might also want to Google "UIAutomationCore.dll FSX crash".  There is a Windows dll that does not work well with FSX (which was originally written to run on XP.)  This problem can also cause crashes when using menus, reloading flights, etc. on Windows 7 PCs.
Back to top
Profile PM 
higgy_de
(HC722HI)
Offline





Group: Member
Posts: 26
Joined: Jan. 2017
Posted: Feb. 04 2017,01:23

thanks, i will try

--------------
regards, Higgy
Back to top
Profile PM 
higgy_de
(HC722HI)
Offline





Group: Member
Posts: 26
Joined: Jan. 2017
Posted: Feb. 04 2017,01:34

try both things :
http://www.fsx-info.de/der-flu....mmer-ab

nothings helps ...


--------------
regards, Higgy
Back to top
Profile PM 
Simon853
(HC685SI)
Offline





Group: Member
Posts: 2307
Joined: Sep. 2005
Posted: Feb. 04 2017,14:03

I didn't mean to suggest that your crash problem with the 206 is solely due to that dll problem, just that it is a known stability issue that can cause some crashes.  I've witnessed it a few times during my testing, but it is a different crash to that which is occurring during the 206 load with FlyInside.

Si
Back to top
Profile PM 
higgy_de
(HC722HI)
Offline





Group: Member
Posts: 26
Joined: Jan. 2017
Posted: Feb. 04 2017,15:24

ok, will wait for your tests :)

--------------
regards, Higgy
Back to top
Profile PM 
Simon853
(HC685SI)
Offline





Group: Member
Posts: 2307
Joined: Sep. 2005
Posted: Feb. 06 2017,21:33

The changes I have tried have not solved the problem, but I have narrowed down the issue to something within my DirectSound implementation, which is used to play sounds that FSX does not natively support.  If I prevent it from initialising DirectSound then it never seems to crash at all, but that's not a fix.  If I delay the loading of DirectSound within the aircraft initialisation then it loads the first time but then crashes on subsequent reloads.  Why this happens when using FlyInside but not without it is now clear, but is likely related to the fact that FlyInside is taking control of the window to which DirectSound is attached.  I am continuing to investigate.

Si
Back to top
Profile PM 
58 replies since Jan. 06 2017,16:38 < Next Oldest | Next Newest >

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

Pages: (3) < 1 [2] 3 >