Jump to content

Tulpenmuster

Members
  • Content Count

    20
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

0 Neutral

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    Other
  • Virtual Airlines
    No

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hello, Maxime! So you made FE9G? Your sky textures and these wonderful SweetFX settings are simply superb. I can't get enough of your sunsets. Combined with the - at least for my humble self - still unsurpassed cloud textures from Flight Environment (personally I really admire all those screenshots with REX clouds, but everytime I tried them, they appealed too imitately, almost cartoonish in my eyes) and more quiet water FS9 is newly born. Thanks a lot for sharing your great work with us! Long live FS9! Jens
  2. Hi, John! Do you search buildings as scenery objects or alternative textures for the default autogen buildings? I you' re searching for textures maybe you take a look at this thread at sim-outhouse: http://www.sim-outhouse.com/sohforums/showthread.php?70289-Replacement-European-Buildings I remember the package, which is described there; it was a bundle of - amongst others - famous freeware koorbygen textures for autogen buildings and freeware Airport Environment Upgrade. Best regards Jens
  3. Graeme, Craig and everybody who cared, my problem is solved. Graeme sent his panel.cfg file to me, but actually it was identically equal to mine. But as requested he kindfully provided his RXPGNS.INI file, too - and that did the trick. I really don't know why it didn't work for me before. I can only suspect that the RXPGNS.INI created after the installation of my RXP GNS430 conflicted with the configurator which Dreamfleet built for the Dakota - and which among others determines what kind of navigation database the GNS is actually using (International or Americas). Without this RXPGNS.INI by Graeme I suffered from CTDs. So, thanks again for your kind help! I appreciate it a lot. Jens This is the RXPGNS.INI that works (maybe it can help others, too): [GNS430] Popup=15431 AutoPilotMode=2 Radios=1 LinkCdiKey=On AutoCdiMode=0 AutoApproach=On LinkVor=1 LcdStyle=Off AutoWidth=500 AutoHeight=210 Trainer= NoKeyClick=Off DisableRxTx=Off AutoPowerOn=Off AutoRadiosOff=On GndSpdFromDeltaLatLon=Off AutoCourse=Off LinkObs=On ShadinFuel=On RadioSyncMode=Full Brightness=-1.000000 CrossFill=Off TCAD=Off Taws=On TawsVolume=60 TAWS_ALRT_TYPE_NEG_CLIMB_RATE=0 TAWS_ALRT_TYPE_IMMINENT_OBST_IMPACT_CAUT=0 TAWS_ALRT_TYPE_REDUCED_OBST_CLEARANCE_CAUT=0 TAWS_ALRT_TYPE_IMMINENT_TERR_IMPACT_CAUT=0 TAWS_ALRT_TYPE_REDUCED_TERR_CLEARANCE_CAUT=0 TAWS_ALRT_TYPE_IMMINENT_OBST_IMPACT_WRNG=0 TAWS_ALRT_TYPE_REDUCED_OBST_CLEARANCE_WRNG=0 TAWS_ALRT_TYPE_IMMINENT_TERR_IMPACT_WRNG=0 TAWS_ALRT_TYPE_REDUCED_TERR_CLEARANCE_WRNG=0 CPU=0 HardwareDevice=Off HardwareIdx=0 [sETTINGS] Dimmer=Off SimpleMouse=Off KeyOnFocus=On [GTX327] AutoStandBy=On AutoStandByDelay=24 VFRCode=1200 AltitudeFormat=FL FlightTimerMode=CLEAR AcftType=LESS_15500 FlightTimer=0.000000 CountUpTimer=0.000000 CountDnTimer=0.000000 CountDnTimerRef=0.000000 AutoPowerOn=Alt Brightness=-1.000000 [GMA340] Brightness=-1.000000
  4. Thanks, Graeme! At least I know now that it really can be done. Since a month - whenever I get round to it - I edit the panel.cfg files (1024,1280 and 1680) of the Dakota, removing all references to the old RXP-gauges. I inserted the newest Flightline-T, Flightline-N, GNS 430-gauges from Reality XP - to no avail. As the GNS 430/530 WAAS gauges from RXP seem to be rather critical, I even supposed it could be a licensing problem or a failed installation. Therefore I did a reinstallation of all the RXP stuff and actually the gauges work in other planes of mine. Grame, or anyone else, would you mind to send me your panel.cfg files or post it here? This would be of great help to me. As I understand from blanked out entries in those files DF expressly allows users to share a modified panel.cfg). Thanks in advance! Jens
  5. Craig, thank you very much for your detailed response - especially for your tip regarding the GNS430_nc1 from Carenado. I indeed own every aircraft from Carenado they made for FS9. Perhaps I will try to transfer their GPS into the Dakota's panel. It seems my descriptions while starting this topic were not clear. Sorry for that. I know that the planes from DF came with their own RXP gauges tied to the particular plane. But the Garmin trainer software, which was always needed by the Garmin suits from RXP, was 8-bit-Software. That was why one had to buy all the expensive gauges once more in their current version, which can be used even with Win7/64 bit. So with help from friendly people like you I managed to revive my A36 and the B58 from DF. But substituting every gauge - even in the 2D panels - does not seem to work in case of the Dakota. It's hard to understand for me. I installed the newest version of GNS430 from RXP and it does a good job in a few other aircraft (including Dreamfleet's A36), but the Dakota refuses to work properly. Any further help is very much appreciated. Thanks
  6. Hello everybody! Thanks god (and AVSIM) for this forum! I'm very happy to see so many people still loving good old FS9. And I know people here (and on a very few other great sites) are very knowledgeable about this sim. Personally I enjoy FS9 even more than 10 years ago. Underway my scenery.cfg grew up to more than 1.500 entries. Hundreds of aircrafts were tested. Wonderful freeware and expensive payware came up. Sometimes ( or should I say often?) it was rather fiddly to make it all fit together...You know the highs and lows of our hobby. In the end it mostly was going well. But now I'm rather frustrated. You know, my everytime GA favorites (besides the outstanding works from RealAir and the later Carenado) were the planes from Dreamfleet. Especially the A36 and the B58 - again and again I come back to them. They're marvellous. After porting over to Win7/64bit I spent much time to make them work again (and I gave even more money away as thereto one has to buy nearly all current products from RealityXP, who - with due to respect - should be praised for their stuff, but blamed for their exorbitant prices). Bert Pieke - he's a fine chap - helped me in particular. So recently I decided even to buy the Dreamfleet Dakota, for all that I knew that DF is as still as a grave. I ignored the warning that the Dakota was developed for Windows XP/32bit, I simply trusted in a chance to change the old gauges, the Dakota originally comes with, against the already bought new gauges from RXP. Because with some effort even the A36 and B58 worked fine. Unfortunately this confident mood didn't last very long. My sim was nearly loved to death by this install. For first time I had scenery.cfg file errors (!), when starting an aircraft ( curiously enough only DF B58). I checked the scenery.cfg multiple times. All fine. Even Scenery Config Editor (great tool btw!) stated: "no errors". Every attempt to start the Dakota ended with CTD. After reinstalling the RXP-Gauges, deleting all scenery.dat files and most of all uninstalling the Dakota my sim recovered. Afterwards I installed the Dakota again without installing the old RXP-gauges. FS9 hung up during start. Replacing every gauge didn't solve the problem. But now I also suffered OOMs, which I luckily never had before. The Dakota is stubborn. Only if I delete all the 2d panels and views in the panel.cfg I even can load the Dakota and go flying with her. But then every attempt to enter the menu or change to another aircraft leads to a CTD. By no means stable. I assume that the Aircraft needs the internal config tool provided by DF. I read dozens of threads about the Dakota and other DF products on Win7/64 bit; in the end I'm really confused. With regard to the Dakota it's obviously not enough to substitute the RXP-Gauges and delete every reference made to the old gauges in the panel.cfg. Now my question for you, as I believe many of you like the Dakota and surely have more technical knowledge than me: Is there anybody who can use the Dakota on Win7/64 bit without CTDs? What is your secret? And does anybody fixed the problem that there are nearly no visible vc window reflections? In the A36 and B58 from Dreamfleet the reflections contributed much to immersion, but honestly the Dakota seems unlifelike compared to the other products. Thanks for reading this. Any help is much appreciated. Jens
  7. @Sascha As far as i know, FSHotSFX and FSHotSeat are separate products, whereby FSHotSeat includes all the functions of FSHotSFX and gives you more like a copilot. Please search for fshotseat - they still have a homepage which provides further details even about specs. To bad the program just runs on XP. It surely won't do on a 64bit system. I heard their aisounds once (they call it AiBlast technology) - and for sure it's a blast! Jens
  8. Hi Mel, PM sent. What a great forum! I enjoy it a lot. Nowadays - after more than a decade of tweaking and despair - I love my FS9 more than ever. Nice to see you all share this addiction. Again: Thanks a lot for your kind help! Best wishes! Jens
  9. Hi all! I know, I really come late to this party, but I set my hope on you. Please be lenient with me! I urgently need a patch file to make Holger Samdmann's scenery "Columbia River Gorge compatible" with UT USA (FS9). The file from Holger is called "utusacrg.zip". I tried my best to find it in the web, but all the links I found are no longer valid. Do you still have it in your personal archives and give it to me? Thanks in advance! Your help is very much aprecciated! Jens
×
×
  • Create New...