Jump to content

Jure

Members
  • Content Count

    668
  • Donations

    $0.00 
  • Joined

  • Last visited

Everything posted by Jure

  1. Thank you all for your input! Much appreciated! :) I will stay with FS9, I do have a lot of work to get everything working again but at least I know that it will work. I am getting too old for constant tweaking and setting up instead of flying. I might try something else one day but as you all say, FS9 should stay - and it will. I know ours is a niche hobby, but still, I am left with a somewhat bitter taste in my mouth that after the few years while I was away from simming more progress had not been made. In this turbo world of instant gratification it is to be expected, I guess. On the other hand I have nothing but the utmost respect for all developers in our hobby! And FS9.... my, it was made so long ago and look at it today!? Some features have still not been bettered. Thanks again! :) Jure
  2. Hi to everybody, I am resurrecting this thread because there's no need to start another, I guess. I've started "flying" on the Amiga, then Flight Unlimited came along, and Fly! and FS2002 and... you know the story. I've been away from my FS9 for the past 4 years due to RL stuff but by now, the itch is getting unbearable! So, I said, OK, years have passed, surely there's a better sim out there! Is there? I am simply asking for an advice although after reading this and many other threads, watching many videos showing off P3D, Xplane11, I am not so sure anymore. My reasons are thus: In my FS9.5 as we called it, I flew airliners for 95% of time. I had AES, FlighKeeper, FSNAV, Track-IR, some HW modules, add-on ATC and tons of airports, aircraft and so on. And zero problems. I still have the old rig, it was -is- a dedicated flight sim computer. All I have to do is install FSFK, AES, FSUIPC and a few other things on my other PC and I'm all set. If I can find the license keys for everything, that is. So, am I crazy wanting something else? Among other things I want to fly the old Ralph Tofflemire's B747-200 into Kai-Tak, listen to ATC chatter, see other AC in the air, have a jetway connect to my aircraft at the gate (you DO wave to the AES guy after pushback, don't you? :)). What I don't want is no AES, crappy ATC, no AI, no seasons by default and an investment into a new rig to drive some beast of a sim (P3D?) I answered my own dilemma, I guess... still, I'd love to hear your opinion. Inspite of flying the big tubes I am a sucker for visuals, but the things I mentioned are more important to me than 2.000 autogen buildings and trees per square meter and giant 4K textures where you can see a snail crossing the highway. Immersion like I am used to in the FS9. Can it be had in another sim (X-plane 11 or P3D v4.) or I better stick with the old gal? Or I am hopelessly behind the times? I'm not of FB, you know... ;) Thanks for your thoughts! Jure
  3. Hi Harald, as Geoff wrote there was a mention of SweetFX earlier in november. Take a peek here: http://forum.avsim.n...s-with-d3d9dll/ - specifically, post #6 about a beta Radeon driver with the ability to integrate SweetFX. Maybe it will help with the flickering? Note: I have to install the .dll into the main FS9 folder or else it does not work Note2: SweetFX seems to be very particular about the settings file. I set up mine as FS9.txt and it resides in the main FS9 folder, which is pointed at in the SweetFX_preset.txt file. - FS9 will not start if SweetFX doesn't find the file mentioned in SweetFX_preset.txt or finds something in the text it doesn't like in the settings file. - FS9 will crash if SweetFX finds something that it doesn't like in the settings after you've edited it with FS9 running. Also, FS9 will not start anymore. I had to overwrite my settings file FS9.txt with default values from SweetFX_settings.txt on a couple of occasions just to get FS9 running again. Still not decided if it is better than ENB, though. More testing needed.... :smile: Regards, Jure
  4. Clutch,as promised, here's my VC section:[Vcockpit01]Background_color=0,0,0 size_mm=1024,1024visible=0pixel_size=1024,1024texture=$vc_01gauge00=Boeing777-300!Beacon_Nav_Light_Switch, 861,466,163,102gauge01=Boeing777-300!Master_Caution, 883,909,117,112gauge02=Boeing777-300!Autostart, 862,376,80,91gauge03=Magnetic_Compass!Magnetic-Compass, 869,756,148,150gauge04=PSS-B777!ND_Floater, 464,28,369,387gauge05=PSS-B777!MFD_Floater, 465,519,372,381gauge06=PSS-B777!EICAS_Floater, 31,519,375,383gauge07=PSS-B777!PFD_Floater, 36,37,367,377gauge08=PSS-B777!TrimInd_VC, 899,14,81,352//--------------------------------------------------------[Vcockpit02]file=$vc_02.bmp Background_color=0,0,0 size_mm=1024,1024visible=0pixel_size=1024,1024texture=$vc_02gauge00=Boeing777-300!Backup_Attitude, 441,848,174,174gauge01=Boeing777-300!Clock, 619,854,170,168gauge02=Boeing777-300!Autopilot, 332,528,689,78gauge03=Boeing777-300!Rudder_Trim_Ind, 845,611,179,75gauge04=fs9gps!gps_500, 386,-1,637,527gauge05=Boeing777-300!Comm 1, 2,494,202,84gauge06=Boeing777-300!Comm 2, 2,583,200,83gauge07=Boeing777-300!Transponder, 1,841,200,76gauge08=Boeing777-300!Nav 1, 3,670,200,82gauge09=PSS-B777!AP_ALT_vc, 753,542,87,20gauge10=PSS-B777!AP_HDG_vc, 542,544,64,19gauge11=PSS-B777!AP_SPD_vc, 669,543,63,18gauge12=PSS-B777!AP_VS_vc, 858,545,68,14gauge13=PSS-B777!RadioAct_VC, 25,512,68,19gauge14=PSS-B777!RadioAct_VC, 23, 602 ,68,19gauge15=PSS-B777!RadioStby_VC, 113,513,66,18gauge16=PSS-B777!RadioStby_VC, 110,602,66,18gauge17=PSS-B777!XPDR_VC, 62,849,77,25//--------------------------------------------------------[Vcockpit03]file=$vc_03.bmp Background_color=0,0,0 size_mm=1024,1024visible=0pixel_size=512,512 // <-- use 1024,1024 for more detailed dirt but need more memorytexture=$vc_03gauge00=Pky_glassdirt!Pky_glassdirt, 0,0,1024,1024//--------------------------------------------------------[VCockpit04]size_mm=512,512pixel_size=512,512texture=$Posky_ACUbackground_color=0,0,0gauge00=Posky777!Pky_AdvInit, 140,80,140,80gauge01=Posky777!PkyNosegearheight, 140,80,140,80gauge02=Posky777!PkyLeftgearheight, 140,80,140,80gauge03=Posky777!PkyLeftgearboggie, 140,80,140,80gauge04=Posky777!PkyRightgearheight, 140,80,140,80gauge05=Posky777!PkyRightgearboggie, 140,80,140,80gauge06=Posky777!PkyCALC, 140,80,140,80gauge07=Posky777!PkyWINGROOTFLEX, 140,80,140,80gauge08=Posky777!PkyRWINGMIDFLEX, 140,80,140,80gauge09=Posky777!PkyLWINGMIDFLEX, 140,80,140,80gauge10=Posky777!PkyRWINGTIPFLEX, 140,80,140,80gauge11=Posky777!PkyLWINGTIPFLEX, 140,80,140,80gauge12=Posky777!PkyNosegearsteerling, 140,80,140,80gauge13=Posky777!PkyRudder, 140,80,140,80gauge14=Posky777!Pky2Rudder, 140,80,140,80gauge15=Posky777!PkyflaperonL, 140,80,140,80gauge16=Posky777!PkyflaperonR, 140,80,140,80gauge17=Posky777!PkyLSAileronL, 140,80,140,80gauge18=Posky777!PkyLSAileronR, 140,80,140,80gauge19=Posky777!PkySpoiler, 140,80,140,80gauge20=Posky777!PkyElev, 140,80,140,80gauge21=Posky777!PkyAPUDoor, 140,80,140,80gauge22=Posky777!PkyEngRev, 140,80,140,80Works for me and I have nicely lit VC at night.Ha, now I remembered something.... for lights to be shown correctly, you have to press MASTER BATTERY SWITCH in my case CTRL+ S.H.I.F.T + M. Try that... :smile:Regards,Jure
  5. Nandan, thanks! Will do.... :smile:Regards,Jure
  6. Thanks, Tri! I did two more flights with the -200ER and this time fuel consumption was OK. As much as I could compare it to different sources - I am no expert! :smile:I will play with the -200LR and see what happens. It looks like I get too low consumption on that model alone.. Roger on that, Tri. We have a CAT-III ILS equipped rwy here at my home airport of LJLJ (and loads of dense fog in winter), but I try and land manually nonetheless. You know, the challenge... and since it is a simulator... :(@Clutch:Clutch, I'll post my VC section once I get back from work, you must be missing something in yours. Everything lights up nicely in my VC at night. Regards,Jure
  7. Hi, I noticed the same. Been fiddling & flying with the T7 for the whole week. I made a long flight yesterday, WSSS-KORD, distance 8,541nm, B777-200LR. Fuel consumption was 293,000lbs, which seems low for almost an 18 hour trip. For a 15 hour trip some 305,000lbs of fuel is usually burned (RL data) aboard a -200LR. I did use accelerated time, up to 16x! Maybe that's the reason? On a side note, I reduced the elevator trim effectiveness from 3 to 2 without ill effects (I don't do autoland - what's the point, LOL) and I can trim the T7 nicely now...One way or another I like these tweaks a lot, so thanks again, Tri! :smile:Regards,Jure
  8. Hi Tri!Thank you VERY much indeed for these tweaks! I just flew a test flight aboard an 777-300ER from Singapore to Kai Tak. The T7 worked like a charm and because it was a test flight, I was using accelerated time up to 16x. No more porpoising! How did you manage that I do not know but I am quite happy with that alone. Terrific!I've been tweaking my Posky/PSS merge for ages now and your tweaks are the cherry on top. A few points I'm curious about:- Fuel planning: I used PSS's planner for the -300ER and it worked perfectly. How about the other models? You mentioned that you have tweaked fuel consumption... is PSS's fuel planner still valid? As I said, it worked for the -300ER... but how does the FMC react to changed consumption, do you know? Will it show accurate fuel consumption prediction or were the values for different models "hardwired" by PSS? - You set elevator_trim_effectiveness=3.0. I am using a GoFlight GF-LGTII module with trim wheel and 3.0 made my poor T-7 jump like a rabbit up and down at slightest touch. :( Just curious, why set so high? In my old aircraft.cfg I had it at 0.4- Obviously, PSS loaders won't work (I used to copy the weight & balance section from the PSS aircraft.cfg to my merged .cfg after adjusting pax & cargo.) Any reason for reducing the station_load lines? Again, no biggie at all, you provided No. of pax for each station and that will work nicely. - VC: I tried to put PSS-B777!Autopilot gauge into the VC, but it looks like the VC itself was modeled in such a way that it is impossible. Just wondering if you came to the same conclusions? I am using a panel.cfg virtually identical to yours and with Saitek TQ buttons assignments I have virtually all functions available in the VC (LNAV, VNAV,etc.,...)That's it. I'll switch to your FDE & aircraft.cfg settings over the next days for the rest of the 777 fleet and be happy. :( Again, thank you for your work, I love what you did for the T-7! :( Regards,Jure
  9. Hi Boby,Ok, let's see how I did a custom cfg file for my PSS/Posky B777 merge. You can use this example for every single aircraft in your fleet if you wish.1. find your fs9.cfg in C:\Documents and Settings\USER NAME\Application Data\Microsoft\FS92. Copy it to your main fs folder.3. rename it to FS9_po777.cfg (or whatever you wish)4. I suggest you create a folder on your desktop where you will keep your shortcuts for all custom configurations. Mine is named simply FS5. In this new folder create a new shortcut and name it so that you will know for which aircraft it is intended. In this case, mine is called PSS_Posky_B7776. Fill in "Target" and "Start in" fields as you see on the picture belowWhat is important is the second part in the field "target": the part /CFG:"FS9_po777" tells fs.exe which config file to use. It MUST match the name of the file you just created in your FS9 main folderThe following steps are only valid if you use FSUIPC - registered!7. in Wordpad, open FS9_po777.cfg which you have created in your main FS folder.8. Right on the top, put these two lines (The parenthesis around the word FSUIPC are of course... huh, what's the right word? Well, like all other parenthesis in fs9.cfg, LOL. I cannot use them here. These two lines will tell which FSUIPC.ini to use with your custom settings for this aircraft.{FSUIPC}ControlName=FSUIPC_po7779. Go to your main FS folder/Modules and find FSUIPC.ini and FSUIPC.key10. Make copies of these two files and rename them exactly as you wrote under 8. So, in my example, you have FSUIPC_po777.ini and FSUIPC_po777.key.11. You're done! Double click on your newly created shortcut and if everything is done correctly, just select your chosen aircraft, modify all controls and they will never be changed again. Probably. If FS changes assignements in FS9.cfg or FS9_po777.cfg, you can put a line LOCKED=1 under each JOYSTICK_MAIN.... and JOYSTICK_SLEW.... lines after you have set it up. This will prevent FS from messing with your controller's settings.However, I advise you to assign everything, including the axes through FSUIPC and disable joysticks in FS altogether. Let me know if you have problems, I hope I haven't let anything out. I am using a slightly modified method for my different aircraft where I also copy necessary .dll file(s) from a backup location into the /Modules folder, which is thus kept very clean. Only the necessary .dll gets copied when I start FS9 with a specific .cfg. But that's step two. :(EDIT: as for your question... I am not sure if there is such software. You can use the attribute "This aircraft only" in FSUIPC, but I found out that the FSUIPC.ini quickly becomes totally illegible with multiple aircraft configs, especially if you use some advanced buttons/axes/keypresses programming. I much prefer separate FSUIPC.ini files.Regards,Jure
  10. Hi,yes, I use multiple fs9.cfg and fsuipc.ini files. For each aircraft or aircraft group I have a separate icon. Each of them has custom controls and keys assigned. I am at work right now, but when I am home, I can post a detailed description. Either here or you can send me a mail or a PM. :)Regards,Jure
  11. Bill, Maybe the problem lies with the old FSSound module... Try this:1. Open your fs9.cfg2. Add these two entries (if they are not there yet):(OldModules)FSSound.dll=1The brackets around "Oldmodules" are square. regards,Jure
  12. Confirmed, they do. :)More, I have RC4 running on one machine via WideFS and ASv6.5 on another, again via WideFS. Regards,Jure
  13. Brian,now I feel stupid! Found the culprit...I haven't made a flight yet and somehow, I forgot to plug in my Saitek yoke and pull out the darn Logitech wheel! I have joystick(s) deactivated within FS, because I do all calibrating and assignments within FSUIPC, so I didn't really pay attention.Sorry for cluttering the forum with my stupidity. Bah... :(Thanks for trying to help! All is well now, even with PMDG and the said file active, I can exit FS just fine. Regards,Jure
  14. Brian,just noticed your post when I finally managed to post mine (lost internet connection while I was typing).I tried disabling the file, but fs9.exe still won't exit.Regards,Jure
  15. Hi,first of all, a big THANK YOU for the wonderful Kai Tak scenery!! :)It is working, but I am getting util.dll crashes as well on exit. That is with the PMDG aircraft, with the rest, FS9.exe remains active once I get to desktop and I have to kill the process. The only thing that I did differently is that I didn't install 9D to Addon Scenery, but to a folder where I usually keep my scenery. But that should not affect anything. What I did:1. Uninstalled Kai Tak 98 completely (and VHHH even before that). No traces remain2. Checked and re-checked and then checked again for correct installation. All files are where they are supposed to be, No. of files correct. Renamed everything according to instructions.3. I have no other modified files in Scenery/Asia/Scenery4. I have a few additional files in Scenery/Generic/Scenery. Removed them, FS still crashing.5. Deleted everything in scenery.cfg except 9D and AES.6. Tried with no traffic, also deleted my traffic.bgl (which is by now quite big, 93Mb.)7. No duplicate AFCADS.8. Removed ALL Afcad files from Addon scenery/Scenery9. My /Modules folder is clean, I copy required .dll's there only when required -- I have a few .bat files to do that and then start FS.After all this, FS9 still won't exit properly. Now I am at a loss what else to do... Maybe there is another modified file somewhere in Scenery/World/xxxxx folders that is making problems, I do not know. I do have quite a few add-on sceneries but my FS installation is fairly clean, I know where everything is. Or at least I hope so, LOL.If you guys have any ideas what could be causing this, I would be grateful. It's not a biggie, actually, but kind of annoying. Yesterday, I had four instances of FS9.exe in memory and only noticed that when I tried to install an updated recorder.dll to the /Modules folder and it wouldn't let me, of course. Regards,Jure
  16. It is great, isn't it? If the finished product is anything like seen on the video, I wouldn't mind at all if it is payware. With (hopefully) AES support I will be in FS heaven. But then again, being spoilt by the said AES, the old Kai Tak is about the only airport that I fly to regularly and is not AES-ed.Now I really can't wait, LOL! But take your time, guys, take your time. :)Regards,Jure
  17. This is an interesting thread! :)I had a bunch of problems with my old box, including a RAID 0 failure. I have no desire to reinstall everything anytime soon. FS is running beautifully on a dedicated drive on a computer that does nothing else but FS. I am planning to buy an external drive and make regular backups. The idea of "snapshots" appeals to me a lot. I will certainly take a look at Acronis True Image Home.Thanks guys! :)Regards,Jure
  18. I agree. I only installed Saitek drivers (without SST) for the yoke and all is well.How does it compare to CH? Well, I must say I like it a lot. I have a Pro Flight Yoke and an additional TQ. The Saitek seems much more precise than the CH Yoke ever was. Axes are very smooth. There is a center "zone", like a detent of sorts, but that doesn't interfere with smooth movement of the yoke. It is very well made (at least on the outside, LOL) and double TQs with their six BIG levers look impressive. A lot of buttons to play with, too.Setup:FS can be a pain when it comes to joysticks. Assigning axes and buttons by itself and such, so I disabled joystick(s) in FS completely. All axes were assigned in FSUIPC. Buttons are assigned in FSUIPC as well (a few compound buttons, too - works very well).Calibration:All calibration is done through FSUIPC. The yoke itself doesn't have calibration as we're used to, it calibrates itself. I found out that four levers on the two TQs weren't precisely synchronized, so I had to play a bit with the ranges in Win XP Control panel. Worked like a charm.Well, I have a few fs9.cfg and fsuipc.ini files for different kinds of flying and I couldn't be happier. A typical two engine airliner setuplooks like this:- Yoke axes : ailerons, elevators buttons: TO/GA, elevator trim, landing gear, AP toggle, AT disconnect and such- 2 TQs: 1st lever : Spoilers (including arming detent) 2-3 levers: Throttles 4-5 levers: Reverse thrust 6th lever : Flaps buttons: parking brake, Inc/Dec speed, heading, altitude, VS, Autobrake, doors, etc....- CH Rudder pedals: rudder- Saitek X-45 joystick for the Airbus, choppers, Saab Safir and the likeEverything works great, I don't suffer from random button presses, except on a very few occasions. It sometimes happen on approach, parking brakes get set for some reason, but nothing serious. Just leave the Mode switch unassigned and that's it. Regards,Jure
  19. Kreg,similar thing happened to me a long time ago. I couldn't get it to work properly and rather looked elsewhere for a decent logbook. Found FS Flight Keeper and never looked back. It is one of those "cannot live without it" add-ons. Not to sound like a commercial, but you get many useful things with that program. It is very interesting when you look at the reports and see which aircraft you fly the most, where you fly the most and such. Probably not what you wanted to hear, but as I said, I couldn't get FS logbook to work properly - and I'm glad. :DRegards,Jure
  20. Max,I have the same mesh installed as you and experience no bleed through at either LOWK or LOWS. There must be something else interfering...I suggest a simple experiment:-copy your scenery.cfg to a safe place.-Open scenery.cfg and delete all entries AFTER the "Addon scenery" except your mesh and both, LOWS and LOWK. Renumber these three entries accordingly, save and exit.-Start FS and take a look if the bleed through is still there. If not, then some other scenery is the culprit. To be on the safe side, I suggest that you move all your AFCAD files somewhere safe for the duration of the experiment (if you keep them in one place - I keep mine in Addon Scenery/Scenery).- After you're done, simply copy the original scenery.cfg back in it's place and remove any one offending entry -- if you find one. Fingers crossed! I suggest you use this little program for editing scenery.cfg:SCM2004.zip - Scenery manager, by Hans HartmannRegards,Jure
  21. Clutch, thanks, I forgot about that one! Need to start fiddling with AI again, methinks. :)Here is the entry for VHHX that I use:VHHX,N22* 19.43',E114* 11.64',0I inserted it right after the VHHH entry in Airports.txtBTW, how is the project going? I can't wait.... :)Regards,Jure
  22. Hi, one way to do it is to dissasemble your ai traffic.bgl file with ttools (you can find traffic.bgl in X:FS2004SceneryWorldscenery) then open the file FlightPlans.txt and change all VHHH to VHHX. Save the file and create the traffic.bgl again with Ttools.If you have multiple traffic files, then you will need to do this for all of them! Or at least for all that contain flightplans to VHHH.You do have Kai Tak active, don't you? I suggest you take a look at Jim Vile's magnificent kaitak98.zip file available here at the library. Install everything as he describes and after you're done your AI will follow the curved approach to rwy 13.Ttools is available here as well: ttools202.zipRegards,Jure
  23. Hi,I use this line in my FS9.cfg:LOCKED=1This prevents any changes or re-assignments of the controllers axis and buttons by the sim itself (which happens sometimes) Here is a fragment from one of my many FS9.cfg files... I went to the extremes, deleted any and all setting for my Saitek Yoke, additional Saitek THQ, CH analog pedals and Saitek X-45 joystick and set everything in FSUIPC. Yes, all controllers coexist peacefully. :).*** all leftmost and rightmost brackets should be square, of course ***..(DISPLAY.Device.NVIDIA GeForce 7800 GTX .0)Mode=1280x960x32TriLinear=1(DISPLAY.Device.NVIDIA GeForce 7800 GTX .1)Mode=1280x960x32TriLinear=1(JOYSTICK_MAIN {1C8573C0-8553-11DC-8001-444553540000})LOCKED=1(JOYSTICK_SLEW {1C8573C0-8553-11DC-8001-444553540000})LOCKED=1(JOYSTICK_MAIN {8B4A3700-DE23-11DB-8001-444553540000})LOCKED=1(JOYSTICK_SLEW {8B4A3700-DE23-11DB-8001-444553540000})LOCKED=1(JOYSTICK_MAIN {1C8573C0-8553-11DC-8002-444553540000})LOCKED=1(JOYSTICK_SLEW {1C8573C0-8553-11DC-8002-444553540000})LOCKED=1(JOYSTICK_MAIN {1C8573C0-8553-11DC-8003-444553540000})LOCKED=1(JOYSTICK_SLEW {1C8573C0-8553-11DC-8003-444553540000})LOCKED=1(KEYBOARD_MAIN)SELECT_1=49,8....Regards,Jure
  24. Hi Staffan,wow, thanks for the link! A decent DC-10 coming our way? Or better, an EXCELLENT DC-10 by the look of things. Great!I see that it comes with triple INS system. No FMC, ha! ;) I am curious, are they developing their own, because I can't see a better one than the freeware CIVA INS v.1.51. With which I am having a lot of fun these days. Regards,Jure
  25. Bryan,thank you for the answer. Like Bruno said, it's nothing very important.Doesn't diminish my satisfaction with FS2Crew at all. :)Regards,Jure
×
×
  • Create New...