Sign in to follow this  
Snowfalcon

Anyone figure out how to get the F/A-18 working in RTM?

Recommended Posts

I can't figure out what supporting files are needed to make it work, and I'm not even sure if its possible to make it work without the acceleration installer making the needed changes to the engine.

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

As Jim stated, it cannot be done. It - along with the other two models in Acceleration - require access to the new features embedded in the SP2 Dynamic Link Libraries, as well as the SP2 version of fsx.exe itself.

Share this post


Link to post
Share on other sites

Hi Bill. Thanks for the info. I don't want the Accelerator installed but have the planes and helo installed. I have the P-51 Racer and FA-18 flying OK but the MFD in the FA-18 panel does not work as it needs some stuff from the DLL libraries. I cannot get the EH101 to work at all. It just spins around on the ground. Can I just copy the DLL libraries into my Windows System 32 folder? Best regards, Bob.

Share this post


Link to post
Share on other sites

>I have the>P-51 Racer and FA-18 flying OK but the MFD in the FA-18 panel>does not work as it needs some stuff from the DLL libraries. So you've got the external model showing up correctly on both and the multi stage afterburner working? Can you share how you got these two planes to work?

Share this post


Link to post
Share on other sites

Hi. No I don't have the multi stage afterburner working yet. I have not figured out how to get the MFD gauges working on the FA-18 panel and the EH101 helo is a disaster so far. The P-51 seems to work OK. I hate the fact that there are no 2d panels and that there are no Simicons on the VC panels. If I get a breakthrough I'll post it. Regards, Bob.

Share this post


Link to post
Share on other sites

Wow, talk about trying to violate several copyrights at once.The EULA you agree to is in effect when the software (Acceleration) is installed. It grants you the use of the software (Acceleration). If you uninstall the software (Acceleration), you are actually now not allowed the use of the software (Acceleration). Since the aircraft you're trying to use are part of the software (Acceleration) that you uninstalled, you are in fact guilty of piracy (theft).Oh, and there's quite a bit that doesn't work correctly without the full Acceleration installed. Some of it's far more subtle than the MFD not showing up. ;)

Share this post


Link to post
Share on other sites

Get off your high horse. He paid for the software. And he wouldn't be even attempting it if the package didn't muck up his current installation and/or fail to fix the blurries which sp1 caused, or work reasonably well with current graphics drivers, something which is not discussed on the box or in the literature, of course.Seriously, between this and the way you obnoxiously criticized the flight environment cloud shadows development, you need to think more before you speak.

Share this post


Link to post
Share on other sites

The EULA you agree to is in effect when the software (Acceleration) is installed. It grants you the use of the software (Acceleration). If you uninstall the software (Acceleration), you are actually now not allowed the use of the software (Acceleration). Since the aircraft you're trying to use are part of the software (Acceleration) that you uninstalled, you are in fact guilty of piracy (theft).He may be guilty of violating the Eula in regards to the way it's used, but theft or piracy is a stretch! He didn't steal it, he paid his $29.95. If he uninstalled it, and returned it for a refund, than you would be correct, but as long as he has a paid copy and he's not distributing it, it's not piracy!

Share this post


Link to post
Share on other sites

>Get off your high horse. He paid for the software. And he>wouldn't be even attempting it if the package didn't muck up>his current installation and/or fail to fix the blurries which>sp1 caused, or work reasonably well with current graphics>drivers, something which is not discussed on the box or in the>literature, of course.>>Seriously, between this and the way you obnoxiously criticized>the flight environment cloud shadows development, you need to>think more before you speak. Please... take your own advice.

Share this post


Link to post
Share on other sites

>>He may be guilty of violating the Eula in regards to the way>it's used, but theft or piracy is a stretch! He didn't steal>it, he paid his $29.95. If he uninstalled it, and returned it>for a refund, than you would be correct, but as long as he has>a paid copy and he's not distributing it, it's not piracy!The EULA is a license to use the software. If you violate the EULA it is no longer a license... thus any use of the software is piracy. Please take the time to read the EULA. If you violate it... the agreement is null and void and you no longer have an agreement that allows you to use the software.

Share this post


Link to post
Share on other sites

>>>>He may be guilty of violating the Eula in regards to the way>>it's used, but theft or piracy is a stretch! He didn't steal>>it, he paid his $29.95. If he uninstalled it, and returned>it>>for a refund, than you would be correct, but as long as he>has>>a paid copy and he's not distributing it, it's not piracy!>>The EULA is a license to use the software. If you violate the>EULA it is no longer a license... thus any use of the software>is piracy. Please take the time to read the EULA. If you>violate it... the agreement is null and void and you no longer>have an agreement that allows you to use the software.>Are you being serious? Violating an EULA does not equate to piracy. I think that since he owns a legally purchased copy of the software, I think he should be allowed to install only a portion of the software. Besides, as strict as the FS EULA is, we are still allowed to mod it even when we try to make changes which aren't documented our supported through the SDK. This seems to fall into the same category.Everybody chill.- Martin

Share this post


Link to post
Share on other sites

>>Are you being serious? >Yes, I am.>Violating an EULA does not equate to piracy. I think that>since he owns a legally purchased copy of the software, I>think he should be allowed to install only a portion of the>software. Besides, as strict as the FS EULA is, we are still>allowed to mod it even when we try to make changes which>aren't documented our supported through the SDK. This seems>to fall into the same category.No... he legally purchased a license to use a single copy on a single PC. He doesn't own the software. Period. The license is the EULA. If you violate the EULA, you have no right to use the copy.I'm intimately familiar with EULAs... having taken major corporations to task for trying to find ways around them. I can assure you, that if you violate the EULA, you no longer are licensed to use the software. No exceptions. I can also assure you... you don't own the software.

Share this post


Link to post
Share on other sites

Hi Ed. I bought the Accelerator the first day it was available at Circuit City. I have the box, the CD and the activation key. I did not pirate it like I am sure others have done. There are all kinds of Torrent sites with it. When I saw all of the posts stating what happened to existing aircraft when it was installed I decided not to install it. I saw nothing on the box that stated "Warning- This product might cause damage to some existing installations". Best regards, Bob.

Share this post


Link to post
Share on other sites

>Get off your high horse. He paid for the software. And he>wouldn't be even attempting it if the package didn't muck up>his current installation and/or fail to fix the blurries which>sp1 caused, or work reasonably well with current graphics>drivers, something which is not discussed on the box or in the>literature, of course.>>Seriously, between this and the way you obnoxiously criticized>the flight environment cloud shadows development, you need to>think more before you speak. Hi. Thanks for your post. You are right 100%. I bought it! SP1 caused me some trouble that I did not have on the stock FSX. I had no blurries prior to SP1. That's why I did not want to install the Accelerator. Best regards, Bob.

Share this post


Link to post
Share on other sites

>>>>Are you being serious? >>>>Yes, I am.>>>Violating an EULA does not equate to piracy. I think that>>since he owns a legally purchased copy of the software, I>>think he should be allowed to install only a portion of the>>software. Besides, as strict as the FS EULA is, we are>still>>allowed to mod it even when we try to make changes which>>aren't documented our supported through the SDK. This seems>>to fall into the same category.>>No... he legally purchased a license to use a single copy on a>single PC. He doesn't own the software. Period. The license>is the EULA. If you violate the EULA, you have no right to>use the copy.>>I'm intimately familiar with EULAs... having taken major>corporations to task for trying to find ways around them. I>can assure you, that if you violate the EULA, you no longer>are licensed to use the software. No exceptions. I can also>assure you... you don't own the software.>Yawn...Same old argument - "you don't own the software, you purchased a license, etc". We get it. Whatever - he's still not a pirate, no matter how many times you "assure" me.- Martin

Share this post


Link to post
Share on other sites

>>>>Are you being serious? >>>>Yes, I am.>>>Violating an EULA does not equate to piracy. I think that>>since he owns a legally purchased copy of the software, I>>think he should be allowed to install only a portion of the>>software. Besides, as strict as the FS EULA is, we are>still>>allowed to mod it even when we try to make changes which>>aren't documented our supported through the SDK. This seems>>to fall into the same category.>>No... he legally purchased a license to use a single copy on a>single PC. He doesn't own the software. Period. The license>is the EULA. If you violate the EULA, you have no right to>use the copy.>>I'm intimately familiar with EULAs... having taken major>corporations to task for trying to find ways around them. I>can assure you, that if you violate the EULA, you no longer>are licensed to use the software. No exceptions. I can also>assure you... you don't own the software.>I'm not arguing, he has the right to do this, he doesn't, but that doesn't equate to a crime as piracy and theft is. It is though a breach of contract which doesn't permit you to use the software (or a portion of it) unless you agree to the terms of the license. Violating this, MS could take civil action against you, but not criminal action. Only if he returns it for a refund, and he continues to use it, in this way, or distributes it does it become piracy and a crime.

Share this post


Link to post
Share on other sites

Hi Ed. Since, per you and others, I was supposedly in violation I have since deleted all of the Acceleration files from my FSX that I have tried to get working. As it turns out I had better FA-18's and P-51's with working 2d and VC panels anyway. I did not really want the EH101 as I never fly helos. I hope this puts an end to this thread and that the Moderator locks the thread. Best regards, Bob.

Share this post


Link to post
Share on other sites

I suppose that makes me a pirate for importing my Century of Flight aircraft into FSX? LOL!

Share this post


Link to post
Share on other sites

>Hi Ed. I bought the Accelerator the first day it was>available at Circuit City. I have the box, the CD and the>activation key. I did not pirate it like I am sure others have>done. There are all kinds of Torrent sites with it. When I saw>all of the posts stating what happened to existing aircraft>when it was installed I decided not to install it. I saw>nothing on the box that stated "Warning- This product might>cause damage to some existing installations". Best regards,>Bob. You should be complaining to the developers of those aircraft that are "damaged" and not blame MS.At least to the devs that are selling these aircraft as true FSX versions only to find out they are lame port overs that weren't built using the FSX SDK.Michael

Share this post


Link to post
Share on other sites

>You should be complaining to the developers of those aircraft>that are "damaged" and not blame MS.At least to the devs that>are selling these aircraft as true FSX versions only to find>out they are lame port overs that weren't built using the FSX>SDK.>>MichaelSorry I have to disagree with you here! These aircraft, ran out of the box in the RTM release, and SP1 Patch. It was Aces, that decided to change the rules in the middle of the game! While I realize Aces needs to break backward compatibility at some point, that is something that should have been done at a RTM release. Since it wasn't done at the RTM FSX release, it should have waited until FSXI RTM release, when they could have started with a blank slate. Doing it in a Patch/Addon release is just the wrong time to do something this drastic. Especially for the little gain in graphics and loss of performance we got in Acceleration/SP2. FSX in WinXP far out performs Vista in DX9 or DX10 Preview. IMHO if DX10 wasn't going to be implemented fully, it should have been dropped in SP2 and waited until FSXI, where it could have been implemented the way it was intended to.

Share this post


Link to post
Share on other sites

So far so good for me with Accelleration. The F-18 was definatly a new aircraft with all the carrier ops feature added to the sim. The P-51s also aren't the old CFS P-51 thrown into FSX the new engine controlls and dammage models. The acceleration P-51 has as much in common with the CFS one as "Dago Red" has in common with a stock WWII P-51. So if you whant the new planes you have to install the whole thing. Acceleration has been running fine in both the DX-10 and DX-9 configs for me. I have taken the time to do a couple of small things to keep it smooth.Back up you FSX config file. After installing acceleration delete the FSX confic file and let FSX build a new one.When switching between DX9/DX10 remove the config file and let FSX build a new one.After that reinsert your tweeks.For DX-10 you must have Vista AND a DX-10 compatable vid card. Every FS install needs a little tweaking once you know where your system is happpy it's not that hard to keep it there.

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