almccoyjr

I "envidia" the tech talk getting much more detailed "ati" the discourse more involved as our pc's begin rolling over from the tremendous visual hits Phase 4 will be dishing out, with our study boards begining their slow, stuttering death spirals to the tarmac below, our vc's dead and fans silent with only the sound of code and data whistling through the cables to be finally enveloped in the calming presence of the great BSOD. All will be quit on the Western Front. Dam*; can't wait! plug_nickel

Good points Tamper. The original SLI acronym carried over even though it's function was radically altered and improved. I'd call it, and actually do refer to it as "SVLI", or Scalable Video Link Interface because it's so far removed from the original concept. I think, if memory serves me, that Scan Line went out when PCI was fully incorporated eliminating AGP. The necessary bandwidth was now available to fully render whole sections and then combine them. SVLI comes into its own with higher resolutions and detail textures. A 5-10% gain in performance really needs to be addressed in those terms, IMHO. BHaH/HiTR looks better on my monitor at 2304 x 1440 @80hz than it does at 1600 x 1200 or 1920 x 1200 because of the gain in texture and detail. I haven't been able to pin it down, still doing some research off and on, but the higher the resolution and frequency, the better SVLI performs simply because you're now approaching its capabilities. The old Scan Line was incapable of achieving anything close to that. And if that be the case, then SVLI should be able to enhance many games even though they don't support SVLI. Higher resolutions combined with deeper textures and greater detail "seem" to make a game run better. Unfortunately, marketing seems to have gone down the path of fps performance as a rule of thumb when discussing the benefits of SVLI. The visual gain of 60fps at 1600 x 1200 doesn't compare to 60fps at 2304 x 1440. The kicker with SVLI are the roles the CPU, system ram, drivers and software integration have on the overall benefits of SVLI. Adding a second vc isn't necessarily a performance panacea in and of itself, but higher resolutions can be. plug_nickel

I love the Spad almost as much as my Nupe 17. Where my Nupe is very agile, it still has to be handled somewhat gingerly. The Spad is a tough bird. It'll handle very aggressive Immelmann's, wing-overs and split-s's without nary a whimper or mechanical failure. You can go from breaking off an attack to regaining offensive advantage very quickly and with confidence. The SE5a is very similar according to specs I've read, but I haven't really flown it accept to try it out. Olham's FOV post will help the visibility problem somewhat, but there really isn't a good flying solution to the forward view and a TIR is really needed to fly this plane well. It's really in its element when slashing because it's a very stable gun platform due to its construction. plug_nickel

Sorry for the late post or if I'm beating a dead horse. BSOD's generate the best system info as to why something went bump. Much better than trying to decipher memory dumps. Not to belabor the post, look here: http://www.maximumpc.com/article/features/blue_screen_survival_guide Absolute best info I've seen to date on the subject. Keep a copy of Hiren's CD available as well. plug_nickel

+1 +1 +1 Todays graphic cards do not employ SLI. The way SLI works changed when Nvidia came along. SLI, or Scanline Interleave works by each video card processing alternate lines and then combining them to render a scene. The term SLI was simply continued when explaing how later vc's were linked mechanically and worked to render a scene. Each card now works on a section of the scene and then both combine their output. The CPU and system ram are very important parts of the process. They integrate the video driver, the game developer's software for "SLI" and tell the cards what, when and how to render. The really big difference between the "old" SLI and "new" is that the cards are now capabale of driving insanely high resolutions while delivering tremendous texture details. BUT you have to have the display(s) that have that capability. The best single card of one generation can see a performance gap of 40 to 60% when compared to next-gen vc's running in SLI. Running SLI within the same generation will see much, much less difference in performance. And remember, this performance difference is totally dependent on driver and software efficiency. The other major problems are PSU and the extra heat generated by multiple vc's. The PSU's continuous load rating and matching the needed amperage per rail becomes VERY important. Air flow cooling the cards becomes even more critical if the software is able to sustain the GPU's work load. Parky and Tamper's comments hit several nails on the head. SLI can be of great benefit IF you have the display that will handle high, minimum 1920 x 1200, for base line results. SLi/Crossfire are already running at 3600 on true monitors! SLI is also totally dependent on your choice of gaming, the drivers and the ability of developers to fully utilize SLI potential. plug_nickel ps: How many "old timers" remember or used Voodoo cards in SLI? I remember when 1024 x 768 @70hz was the hallmark of resolutions. 3DFX gave us that.

Go to Java website and follow directions to uninstall Java in Vista-W7. Reboot and then reinstall latest version of JRE. It may not help you being banned, but at least you'll have a clean JRE install. plug_nickel

"GOD spede" to all of you who have been forced to take a different path. plug_nickel

Hey Lou, Add to your list: "What's yours is hers and what's hers is hers"; and Always keep the commode seat down. They have worked well for me for almost 40 years. plug_nickel

You'll also need to be cautious about the heat generated running SLI. PC's running dual, triple or quad v.c's bring to the table their own quirks and problems. plug_nickel

I feel your anger and the pain that will be following. I was laid off back in 5/12/09. I found out that I was in the middle of the 3rd tier, 10-13yrs, for consideration. I was "given" a severance package and later found out from a friend in corporate that I had been only the fourth person to receive one. Now that's just damn sad. The layoffs finally ended at 20 years of service. In the end, 248 people were let go. After the layoff, I could have had a job with other companies IF I was willing to move myself/wife to one of a couple of states located in the northeast, mid-west, west or northwest where there was no family, friends or good neighbors I've come to value. That I wasn't willing to do. It wasn't until this year, this season, that I realized just how lucky and fortunate I was. I've been able to reconnected with "old" friends, have gone to more family reunions, homecomings, and have been able to share the pain of funerals without worrying about "Monday". The time away from work has given way to rediscovering self, wife and all of our families and friends. The money is tight, but having been down that road before, it's not so bad. Good will come if you let it; just don't let the anger turn. As to your question of why: good question. It would probably be better to put your inquiry about the "financial maestrom" and "neoliberalism" in another forum where the resulting impact of so many zeros have had on the pluses of the world could be openly and honestly hashed out. And there are just just to many zeros in the world now. Be it government or business, their impact has become devastating. I hope everything works out. plug_nickel

7-Zip is free and comes in both 32/64 bit versions. WinRAR has their 4 beta now up with a 45 day trial to evaluate. Glad you made it back up! plug_nickel

W7 comes Dx11 compatible. The v.c. that your pc ships with will determine the dx version loaded: dx10/.1 or 11, presuming it's built with a later model v.c. CfS3/OFF needs dx8.1 or later to properly load and and run so before you do anything, check to see what dx version is loaded. Running dxdiag won't help here unless you "peel back" some of the code. To find out what version is loaded go to C:Windows > System32 and look for "d3dxxx.dll". More than likely, you'll only find "d3d10 or 11.dll", which means you're running dx10/11. Now some games will run ok even if dx10/11 is only loaded: the kernal contains SOME code to run older games, but for the most part, it's broken. the same goes for Dx10/.1. The best thing to do is download and install the Dx9.0c redistributable from MS. That's why MS, "in its wisdom", finally decided to release it: it fills and fixes the holes that Dx10/11 created. This will enable support back to dx8. You can verify that by going back into System32. The first dx version listed will be "d3d8thk.dll" and will stop at "d3d11.dll". Running dxdiag will only show the Dx11 version listed since it defaults to the latest version loaded. It's been a long time since I've installed CFS3 and I don't remember if the CD set offers the the option to load dx8 or later and I don't have the DVD, so maybe another flyer can chime in add... plug_nickel

Take a look at this forum and go to section on virtual address space x86 (32 bit) http://www.simforums.com/forums/setting-up-fsx-and-how-to-tune-it_topic29041.html plug_nickel

Tamper and Cody Coyote offer excellent advice about having it built locally. Monarch was outstanding in that respect. Check out some local, reputable shops and inquire about building your system with you observing and taking notes. It may cost a few dollars more, but in the long run, you'll have gained some invaluable experience about the products used, pros and cons that any builder must decide on, wiring and properly setting up the system's bios. Call it: Computer Shop 101. The "educational expense" will be well worth it. You'll find that having done so, you'll be much more knowledgeable and competent when it comes time to scratch that upgrade itch. Happy shopping! plug_nickel

Stupid questions on my part, but did you install the patches for BHaH and have you activated the pilot you're going to use? plug_nickel

There are three areas to configure. The first is the CFS3Config setup. The second is the Pilot Dossier and the third is in Workshop. Do you have a pilot setup? plug_nickel

To ensure that the Dx9.0c redis installed correctly, go to C > Windows > System32 and scroll down to "d" listings. I thought the earliest version serviced was Dx7 legacy but it doesn't. Dx9.0c installed links will start with "d3d8thk.dll" and will follow in order to "d3d11.dll". This last file is the version that dxdiag references. plug_nickel

I know exactly what you're feeling. When David Lance Arneson passed away, so did my feelings for the like. So it's "Hear, Hear" for all the good memories. plug_nickel

OUCH....Been there before and since I like dealing with pc's, I'll be going there again as "things" get more complicated. CFS3.1a updated requires Dx8. I believe OFF uses more of the features that later Dx versions offer. Just to let you know, I'm running W7 ULT_64 with Dx9.0c redist and Dx11 and have no issues what so ever with OFF/HiTR. Since OFF does pull some data from CFS3.1(a), it might be that the necessary .dll/.sys/.mui files aren't there for OFF to use. The DVD version of CFS3 had Dx8.1 on it, maybe even Dx9.0, since it was offered much later than the 2 disc setup. Dx9.0c services legacy 8.1 so that won't be an issue going forward. Since I don't have the DVD, this is just a reasoned guess on my part. You might be better to do a full, complete wipe of CFS3 and OFF and start over from scratch. Use the FAQ before proceeding with that. If it's not done correctly, you're in for some head scratching surprises. Before you do, run dxdiag and confirm drivers and support. plug_nickel

Did you install the latest 9.0c redistributable or just a DX 9.0c from Softpedia or the like? The redistributable was wriiten by MS to specifically "plug" all the holes Dx10/.1 and 11 had and the latest 9.0c services Dx all the way back to v7. The latest one, I believe, is dated June/2010. You may have to due a full uninstall/reinstall of OFF because I'm not sure if the Dx libraries will link after the fact or not. I've never tried. With all the bruhaha about Dx10/11, I've just always installed the latest redistributable before installing any program that required legacy Dx. Just some thoughts and my 5 cents worth. plug_nickel

WoW! Monarch Computer; as in the butterfly logo? If so, they were just down the road from where I once worked. Back in 2000-2002, I would pay a tech I knew to instruct/supervise when I wanted o.c. my pc. With his help, we were able to boot DOS 6.0, Redhat, WIN98SE and WIN2K Pro. Learned some bios "tricks" as well. Good times. Sad they went bankrupt. At least the knowledge imparted hasn't gone Chapter 7. Their tech people were top notch IMHO. plug_nickel

For me, using a hat switch for dynamic viewing is like using the keyboard to control the dynamics of flying, it just doesn't work well. There are many who use the hat switch very well; I was one of them. I even wrote a script for my COUGAR to change to different panning speeds using S3; however, it was still very mechanical. TIR changed that and made dynamic viewing much more realistic. Yes, it's still mechanical, but the "intrusiveness" has been greatly diminished compared to using a coolie. You've got a very good TIR. It'll make your simming that much more enjoyable just like a HOTAS did. Since you're using TIR5, try this. Startup your TIR, hat on and set the template to deadzone and axis to Yaw. Then in the DISPLAY box, drop down a make sure 3D, First Person. and Show Hud are checked. Then check Rear as well and Show Pano. This will give you a visual representation, 3rd person perspective as you will, of yourself looking forward while in the cockpit. You'll be viewing yourself from the rear. As you being to SLOWLY move your head, use your eyes only and look over to the left at the 6DOF chart. You'll be able to see the software correlate movement to degree. When you've got a good feel as to how it works, do the same for Pitch and Roll axes. Go back and for and try different head movements. When you feel comfortable with that, change the template to Smooth and start the process all over again. Show Pano loads a visual cockpit mesh for reference. When you're ready, Load Pano loads a profile so you can judge how the profile will work before you start to fly in the sim. You'll have a pretty good idea how your inputs, adjustments work and it'll help you to tweak the TIR when you bounce between flying and tweaking your visuals. In doing so, you'll begin to get a pretty good understanding for head movement, how acceleration affects viewing and have a pretty good "mechanical" feel for head movement and degree of viewing. From this you can move into modifying a template, combining Deadzone control points with Smoothing and if you REALLY want to get adventuresome, adding different numbers of control points to different axes. I call that "TIR Scripting" for lack of better description. AND I do know of "near vertigo"; for the first couple of weeks after DOOM came out, I spent almost as much time using a wastebasket as I did prowling the corridors. The same thing happened when I first started using TIR. I've always wondered how many future aces lost it the first time they went up. plug_nickel

I do the same. TrackIR 4 PRO with COUGAR HOTAS. I use 3:o'clock for back over right shoulder and 9: for back over left shoulder. All other inputs to coolie are nulled out. For situational awareness, I still view with TIR4, but when in a dogfight with someone on my six, I want to concentrate on what's in front and slightly to the sides. I'll snap view back for a quick check to see where they are during evasive maneuvers. plug_nickel

If his gunsmithing is half as good as his CH mods for the Lefty HOTAS are, he's going to have some mighty happy customers. plug_nickel

I'll have to pass on the nibbly bits; my wife has me on a diet and rightly so.....sigh.....However, I did sneak a good taste of some stout! Cheers! plug_nickel