FSX-SE Eaglesoft Citation X 2.0 in FSX SE

[FlavioSSA 44]

Hello everybody,

Quick question, does anybody managed to get Eaglesoft Citation X 2.0 works ok on FSX SE with win8?

The instalation works ok (It don´t find FSX folder, but we can point it out), but when starts FSX and choose the plane, FSX SE freezes. Already did the "Problem Reporting Settings" thing and the plane loads but stutters a lot within the simulator and sound becames intermitent. This shows me that the "Problem Reporting Settings" is only a work around to get FSX continue working without freeze and not the solution itself.

 

Info:

- Don´t have win defender

- Don´t have Microsoft Security Essentials soft.

- Antivirus is disable on the tests

- FSX SE is outside the windows protected folder structure. (It´s alone in another partition)

- Running FSX with admin rights all the time

- Everthing else works ok (Aerosoft addons, A2A, Opus, GSX. FTX, etc)

- Installed simconnect here for addon compatibility purposes: xx:\Steam\steamapps\common\FSX\SDK\Core Utilities Kit\SimConnect SDK\lib

 

So, the question is: is there another way to make it works?

Thanks!

[N400QW 205]

We've not tested w/SE but it's designed for FSX so suspect the issue is Win8 which is unsupported by ES. B)

[n4gix 4,947]

I have tested the CXv2.0 in FSX:SE, but only in a stand-alone running Win7 x64. As soon as I install FSX:SE on my main sim computer as a side-by-side, I test the CXv2.0 in that environment as well.

[FlavioSSA 44]

Thanks for the answers. Mr. Bill, nice that you´re going to test it for sure, but i think you´re using win7, correct?

My suspicious is that all the problems is with the relation between win8 x flight1 DRM system. It´s too mutch coincidence that the flight1 addons that don´t work in win8 has the same issues (or very close), the same erratic symptoms. For example, it´s exactly the same with leveld767. Milviz F15 appears to be the same. Again, flight1 wrapper.

 

As Eaglesoft uses flight1 app, i think it the problem is there. Nothing wrong with eaglesoft plane itself, but with the system that protects it. Somewhere that i don´t remember now, it was said that flight1 drm system was build for winxp, and today the libraries to make it run correctly is not available natively in windows anymore. Maybe it´s a path to follow. What i know is that i miss too mutch eaglesoft planes in win8, and if this path is correct, i think it will not work on win10 either. Future will tell.

 

Maybe, you guys, the developers knows better, but with logical thinking someone can figure it out to all of us.

[N2056 33]

Have you been to the Eaglesoft forums? There is some info there regarding Win8 that could help.

[N400QW 205]

That info is from a suspected IT Pro who uses win8 on a Mac Bootstrap I believe...

We know it's not the CX or the F1 wrapper but rather the way win8 and FSX/SE interact to the extent that many users can't enjoy simming with our or others products on the Win8 platform. :blink:

[FlavioSSA 44]

No, it´s not: http://www.sim-outhouse.com/sohforums/showthread.php?90621-ALS-Flanker

The ALS Flanker uses ...... flight1 wrapper security.

 

... can't enjoy simming with our or others products on the Win8 platform. :blink:

 

That´s true. 99% of them are flight1 wrapper products.

[N400QW 205]

It's a New Year and we aren't starting it with an argument.

For the benefit of others who may observe this we'll simply say that we do not support Win8 as a viable OS for use with FSX/SE.

 

This is a matter of record from all of 2014 and continues. One need only drill down to the Win8 forum here at Avsim to observe the reasons for our refusal.. The F1 Wrapper has, in our experience, never, ever been problematic with Win7 and FSX/SE or even P3DV2.4  B)

 

Edit: The 99% statement begs verification. Do you have stats to back the statement?

[FlavioSSA 44]

Hi, i´m not trying to start an argument. I´m trying to focus and determine where the problem really is. At this point, my suspicious goes all to the f1 wrapper x Win8 "fight". I have the following "not-working" f1 products:

 

- F1 Mustang

- F1 KingAir

- F1 ALS Flanker

- F1 ALS Mirage

- F1 Milviz F15

- F1 LevelD 767

- F1 Eaglesoft Citation X (Not tested CJ1+ yet)

- F1 ATR

 

"F1" is only to say that it uses the wrapper, not necessary a Flight1 product.

 

I can say for sure to what f1 products i have. ALL of them has the same syntoms, freezes and sttuters when choosen in the planes list. Too mutch coincidence for me. Yes, there are other products not working by now, like PMDG products. But they already said that it will be fixed soon. And in their case the problem is with P3D and FSX SE, not win8.

 

Saying that win8 is not a FS friendly platform is another thing i can´t go, because there are countless addons working perfectly. Even the more detailed ones, like Aerosoft Airbus, SSW, RealAir, OrbX, Majestic, Ifly, etc.... FSX SE runs perfectly well in it too. Even if the problem is with win8, what in it is really the problem? Not the entire win8 for sure. What module, DLL, EXE is the cause? To determine where the problem really is don´t implies that a solution must be created at all.

 

I posted this here in Avsim and not in ES forum, because as you stated, Eaglesoft don´t support win8. Maybe here, someone can point a not official solution as the "Problem Reporting Settings" non-official solution. Or at least, post some clues to point where the problem really is. That´s what i´m doing now opening this topic and saying what i think using the tools i have in hand.

 

Happy new year to all Eaglesoft staff

[N400QW 205]

Happy New Year to you as well. B)

Flavio, your assertion that F1 is the only common denominator here ignores the fact that Win8 OS is problematic with FSX out of the box.

 

While Win8 can and is being made to work with various sim platforms/vendor products including our own does not mean that Win8 users aren't facing challenges which they have to solve.

 

We are staying w/Win7 64bit until MS offers a better OS than Win8... B)

[JRBarrett 3,034]

I may be completely wrong, but I thought that the F1 wrapper was just that - a "wrapper" for the actual installer file - sort of like an encrypted zip archive.

 

Once you unlock the wrapper by entering your payment info (credit card), or by it pointing to an existing licence file (for re-installing a previous purchase) it extracts the installer itself which you may then run separately. Once the actual installer is extracted, the wrapper's "work is done", so to speak.

 

It's not "active" DRM like the Couatl service that is used to activate various FSDT products for example, and which requires a specific DLL to be present in the FSX installation.

 

Ron: FWIW, the Citation X runs perfectly on my Win 7/64 standalone (FSX-SE only) installation - just as it did in original FSX running under Win 7.

[FlavioSSA 44]

F1 Wrapper is an active drm as you need the file .lic to stay and be verified all the time you loads the addon. That's the part we can see. I don't know at the moment if f1 wrapper do other hidden checks.

 

We know that citationx works perfectly in win7. What um trying to find is whats wrong when using f1 addons with win8.

[N400QW 205]

I may be completely wrong, but I thought that the F1 wrapper was just that - a "wrapper" for the actual installer file - sort of like an encrypted zip archive.

 

Once you unlock the wrapper by entering your payment info (credit card), or by it pointing to an existing licence file (for re-installing a previous purchase) it extracts the installer itself which you may then run separately. Once the actual installer is extracted, the wrapper's "work is done", so to speak.

 

It's not "active" DRM like the Couatl service that is used to activate various FSDT products for example, and which requires a specific DLL to be present in the FSX installation.

 

Ron: FWIW, the Citation X runs perfectly on my Win 7/64 standalone (FSX-SE only) installation - just as it did in original FSX running under Win 7.

Correct Jim and we're glad to hear that CX runs just as well on FSX/SE as it does on the original FSX. Not surprised, just pleased. B)

 

We know that Citationx works perfectly in win7. What um trying to find is whats wrong when using f1 addons with win8.

The issue under Win8 is part of the challenges we've mentioned for Win8 users and is not related to the CX or F1 in our view. :rolleyes:

[FlavioSSA 44]

I have some news:
With the much appreciated help of Milviz staff (Precisely Mr. Colin), i was able to do tests with addons using F1 Wrapper and my conclusion is very clear: F1 DRM is the responsable of addons using their method don´t work in win8.

The test was simple: In a computer running win8.1 64 bits i installed Milviz F15 with F1 wrapper and Milviz F15 direct EXE install. Both using an almost vanila FSX Steam Edition. First installed the version with F1 Wrapper. Installation ok, when choose the plane inside FS, it immediately freezes. Uninstalled F1 wrapped F15. Deleted all files associated with it. Installed F15 direct EXE installer. And ..... plane working perfectly inside FS. No freezes, nothing. Did the same thing 3 times to be sure. It´s pretty black and white. F1 DRM is interfering with the addons in win8.



Look, i don´t have anything to gain with this. For the contrary, it´s a confirmation that i can´t use my F1 wrapper addons. The developers can do whatever they want with this information. Or just do nothing. For me, it´s a confirmation and i´m sharing it with the comunity. For example, i´m sure that if anybody installs any of the addons i said in the beginning of this tread without the F1 wrapper, i say it will work as the syntoms is pretty much the same.

As said before, i did the tests with the tools i have in hand. A logical test. And a logical conclusion. Just it. Of course, i´m open to debate this, as i think some guys will do

 

Thanks again to Mr. Colin from Milviz.
Thanks for reading.
 

[JRBarrett 3,034]

Interesting finding Flavio! I always thought that the installer that is extracted from a Flight1 wrapper is the same installer that you would get if you obtained the file directly from the vendor in non-wrapper form. (For those vendors that offer both delivery options) - but apparently there is more to it than that where Win 8.1 is concerned.