Jump to content

carlito777

Members
  • Content Count

    1,518
  • Donations

    $0.00 
  • Joined

  • Last visited

Everything posted by carlito777

  1. New Orbx installers (finally Juneau!!!): WA79, PAJN, LKHV, CNK4, YWVA http://www.orbxsystems.com/forum/topic/113096-new-installers-p3dv3-wa79-pajn-lkhv-cnk4-ywva/
  2. Then, I guess, you are better off buying a Carenado planes. Those are exactly for the type of simmer you seem to be...
  3. I am absolutely with the OP as I was also looking for a replacement for my Saitek Pro Flight yoke. From all that I have read (and that was quite a lot), I think that the best yoke you can buy at the moment (which is not force-feedback) is the Yoko yoke. Froogle and D'Andre from AirDailyX did review videos on it and it really looks like an awesome yoke. I already had my credit card ready and contacted Virtual Fly to order one. But then I went a different route... I modded my old Saitek yoke as explained here: http://www.avsim.com/topic/351529-finally-a-fix-for-the-saitek-pro-flight-yoke-pitch-axis/ I have to say it is absolutely amazing. Almost zero cost for the mod (except the two springs) and the difference feels like night and day. No more deadzones and very fluid operations. The mod is really easy and absolutely worth it. Saved me 1000 Euros.
  4. The change in the Cloud.fx file is done by REX. This has been discussed in another thread. I really don't like that REX messes around with shaders without notifying or asking the user...
  5. The release notes mention a fix for the popcorn clouds in Prepar3d v3.1 and v3.2. I'm really curious to see whether the clouds look better now. Keeping fingers crossed...
  6. Hi Chris, yes, I always check the spam folder. Had the same problem registering to the Taxi2Gate forum. Some emails just don't seem to get through to German mail servers. Don't know what the problem is. I just logged in successfully. Thanks! I'm very much looking forward to doing some nice night flying in the next days. I hope, I can get it a bit smoother because it looks absolutely gorgeous! Thanks!
  7. Hi, I bought Night Environment Germany yesterday, but somehow I can't register to the NE forum. I never get the confirmation email to confirm my registration. Tried two different mail addresses. Does anybody know what is going on? Btw, I get very nice performance but some long frames (stutters) in turns with the PMDG NGX.
  8. Don't know about the increase in vegetation but if you install the scenery update you definitely have to reinstall FTX Global. And i think I read somewhere that you also have to reinstall the FTX Trees HD if you use those.
  9. Sorry, but the slightest bit of common sense would have told you that sharing a link to a beta file on a public forum is not right.
  10. See here: http://www.avsim.com...-out/?p=3386995 And scroll down to my post.
  11. You have to update content as well. Same problem as with GSX and SODE.
  12. Some people are just too paranoid. For me at least, you can easily find out what I do for a living by just googling my name...
  13. I'm a finance professor.
  14. I simply made a backup of the Prepar3D folder before running the updates and used the free program Winmerge to compare.
  15. I took the plunge this afternoon and installed the client as well as the content update and compared the files before and after the installations to determine what is changed and what one has to do so that all add-ons work properly after install. Client update When updating the client, apart from the core P3D files, the installer only updates files in the ShadersHLSL directory. This also affects files from PrecipitFX so a reinstall of PrecipitFX is also required when updating only the client. Content update Here comes the more interesting part. I compared most of the files in the following P3D sub-directories to identify the changes made by the content installer: ../Autogen ../Effects ../Fonts ../gauges ../ShadersHLSL ../SimObjects ../Scenery ../Sound ../Texture And this are the findings: Autogen The content installer does replace the autogen definitions. However, to restore them you only have to run FTX Central and switch regions. That’s it. No need to backup the Autogen folder. Effects The installer will replace a lot of the effects with newer files. Nothing is deleted. So I would recommend doing nothing as copying back an old backup of Effects would replace the newer files by older ones. Only thing you need to do is reinstall PrecipitFX to get back these effects. Gauges and Simobjects The installer does a couple of changes to the default aircraft. However, none of the add-on aircrafts is affected. Sound Some wind sounds are replaced. I would assume that if you install REX sounds then they will be replaced again. Texture The installer replaces a lot of the texture files but does not delete any additional files put in there by third party add-ons. This means you definitely have to reinstall your REX textures (after they have provided the required update for 3.2). Also if you own Airport Graphics HD you need to reinstall this. That’s it. Other folders are not affected. So in a nutshell what you need to do after updating the content is: Set a region in FTX Central to fix your autogen files Reinstall PrecipitFX Reinstall REX textures Reinstall Airport Graphics HD So no need to backup and copy any files! And also no need to reinstall FTX Global! Hope this helps…
  16. Just to avoid further confusion: This is plain out wrong! As clearly stated in the instructions from LM you MUST uninstall the Prepar3d v3.1 client prior to installing the new Prepar3d v3.2 client. Otherwise you will have a crippled P3D installation. This has already been discussed various times when LM released the update from 3.0->3.1 last year and those who did not uninstall all ended up with broken P3D installation. So just do NOT install the new client without uninstalling the old one.
  17. Sorry to say, but it is not as easy as it might sound. As I have pointed out above, the Texture folder also contains files from Orbx regions. So if the content installer messes with the Texture folder, then it might also cripple Orbx region installs. In this case it would not be sufficient to simply reinstall Orbx Global. And the content installer is necessary to get a working GSX install...
  18. Hi Rob. Thanks for the input. Much appreciated. One question on the Texture folder: Does the content installer delete the Texture folder and recreate a default one? I'm asking because there are also Orbx textures in the main Texture folder (e.g. ORBX_NCA_BLDA2.dds) and I don't want to loose them. And concerning Autogen: If I backup the old Autogen folder and overwrite the new one after installing the Content part, don't I run the risk of loosing some new files from Prepar3d v3.2? Sorry to ask that many questions but I don't want to screw my P3D installation. Thanks for your help!
  19. So reinstalling FTX Global is not required if you only install Client and Content, right? But a backup and copy of the Autogen folder is still required like others have indicated, no?
  20. Thanks, Rob. Isn't there a program which can do a snapshot of all file names, file sizes and dates in a certain directory before and after an install and then automatically identify what the installation has changed? That would be extremely helpful here...
  21. Another happy GSX user here who is a bit worried about updating the content package. @Rob: Do you have any specific information which files and directories are touched by the content installer? Some say, you need to reinstall FTX Global after updating content. Other say you don't need to. What about the necessity to backup the autogen folder? Don't the FTX regions also put files in there? I'm not very happy that I need to go down that route to get GSX working again... But hey. On the other hand this is the price you have to pay if you want progress, right?
  22. I had the same problem, but I don't remember 100% how I fixed it. I think, I went into the settings where you can specify the path to the scenery.cfg. Even though the path was in there correctly, it still didn't work. As far as I remember, I went into the context menu for the path and simply set the path again (to the same location) and then it worked. But as I said, I'm not 100% sure if this was the solution. But there was a rather easy fix for it. Maybe you can give it a try...
  23. There is a much cheaper alternative. Look for Mark Foti in the AVSIM library.
×
×
  • Create New...