beers

it is a bit much for any of us to tell you that you will like it. Flight-sims are very different from any "game" I ever played, some of my friends with whom I share many gaming interests have absolutely no interest in flight sims. They see them as boring. I have had less-exciting flights and more-exciting flights, but some of my most extreme pucker-moments in life, let alone computer gaming, have been afforded me by the beautiful simulator. i.e. many people do NOT find this boring. Then there is the question if you are going to play on-line with others or just fly by yourself. I enjoy both, as do quite a few people from what I can tell. I know a few who would not start up the sim unless they were going to join others on-line. I think there is a significant portion (a majority?) of people who only fly off-line. The two experiences are worlds apart in many ways, and you might love/like/hate them in different ways. I have never upgraded from the Siatek x52 and it works fine enough. Track IR is essential to me in flight sims, but lots of folks who love this sim do not have any head-tracking, so it's not essential. So, unless you have $750 burning a hole in your pocket, start slow in investing in this hobby. :pilotfly: BTW, you did not mention your rig stat's in your post, you might want to consult some of the hardware threads to see if your rig might require some investment in order to pump out the FPS.

Yes, completely possible to run a Windows machine with only SSD. It's a question of the amount of money you are willing to invest in your system. I have a 55gb SSD that is my boot drive, a few apps (including MS Office) and DCS (A-10 and BS), and I am left with 14gb free on that drive. If you need more space then you have two options; invest more money in a bigger SSD or use HDD in addition to the SSD.

Confirmed!! the regedit's GregP pointed to do the trick for me too. Thank you thank you thank you!

I think PeterP might be on to something with that 32/64 idea. Are those of you with success running 32? I'm running A10 1.1.1.0, BS2 and nvidia 285.62 (and PeterP, i totally agree. "if" "I think", ... i would be more than happy if someone illustrates what setting or whatever that could fix the problem.)

LOL Hellfinger's cute pink slippers :D

Well, if no one speaks up with verification of successful implementation of nVidia stereoscopic 3D then I think our good friends at ED should consider this a bug. It worked in previous versions of BS and A-10C. And, damn, those 120hz 3D monitors are getting cheaper, would have been a nifty holiday season present to myself ... guess that will wait a few more months :(

I think I might have spoken too soon, I cannot get Nvidia 3D to work with BS2 or A10 1.1.1.0. I am just using the "3D Vision Discover", the red & blue glasses, and when either program starts it has the odd slightly-red tint to everything, and the normal messages display, 3D keyboard shortcuts work so I am sure that stereoscopic 3D is in action, but there is no off-set in the image no matter what I do with the depth (or the convergence). The test patterns & sample picture work fine but no DCS 3D. DCS is just the normal image with weird colors. :( Anyone have any luck?

I don't think goldfinger's FPS are representative. See my specs in sig; I get 45-60 fps engines dead, sitting on the runway. Even when i down my clock back to the default 3.4 my FPS doesn't go below 30. I've got my GTX 560ti clocked at 960 core, 1920 shader, 2250 memory. (Note that the sky in those screen shots is overcast, which I find to be the most FPS demanding weather.) IIRC the change is that HDR goes to 'normal', so if you had it on warm or cool you will see a difference in the quality of the image, and that's what you're seeing. If there is a change to FPS it is minor and it's more about your HDR settings than anything else. I have to wonder, with a 3.8 CPU, how do you get such low FPS??? Do you have anisotropic at 16 and AA at 32 or what??? Not familiar with ATI cards at all, is the 4890 old?

It is primarily a feature of the video card. With nVidia you can do the red/blue glasses without the special monitor. The step up from that requires a monitor that will do 120Hz refresh rate and active glasses that sync to the screen. If your card will do it your nVidia control panel will have a 'set up stereoscopic 3D' item on the left. If you have a pair of the red/blue glasses it is worth playing around with for a few minutes.

more than $1000 for a stick is not a solution for any/many of us here. Could anyone provide some video or any more details of why the G940 is a problem (mainly I am interested in BS but A10 would be interesting as well). To what extent does it "not work right" (currently, in BS2).

I think this is one of the coolest things I have ever seen; http://www.xheli.com/aepivifiviwh.html obviously this is different than what you're talking about, but the main component is the headset; "ARV1000-A w/ AVR510 VIDEO GOGGLE Display, integrated with heading tracking gyro control sensor". limited by "640H*480V*RGB" ... rgb? really? but otherwise, awesome.

Yes, been able to use 3D vision (red/blue glasses) since first release of BS, works fine in A10 as well. just turn it on in the nvidia settings and then clear your desk area of any spillable, because after about 5 minutes in there, your connection to the 'real' world gets a bit fuzzy ;) If you can view the sample 3d picts and the setup animation you should be able to do DCS in 3D. Kicks frames in the gut, but you might be able to get reasonable frames with it in SLI (although I imagine if the sli-cloud thing is still an issue that this will give you headaches)

*bump* Any suggestions? I'm sick of imagining how cool BS could be with FFB, but I don't want to get tangled up in the G-940 mess, if it is still a mess...

seems that e-shop is not working properly with Firefox, works fine with MS_IE

" " same troubles ever since updating nvidia drivers to latest 280x release. updated to 285 beta, trouble is less frequent but still happening. never had those problems before. not so much of a problem at the moment, so i'll probably wait for the 285 to come out of beta and see how that works before is start really working on the fix. (unless a fix drops out of the sky and lands on this forum)

keep in mind; http://www.huffingtonpost.com/2011/08/01/chris-staniforth-xbox-death-blood-clot_n_914964.html don't go for more than 12 hours per gamin session ;)

Good, good, i thought i was the only one :music_whistling:

have had g930 for several weeks, great sound, comfortable wearing for hours, only bummer is any microwave oven within 30 feet can disrupt the signal.

Tire squeals when coming to a stop at the parking area...

I had not tried that specific mission. sorry, i guess i was just guessing. Also, never tried things with "easy comms", i'd expect that would negate the mic switch portion of things, probably even the freq. ... I use the JTAC in the campaign missions all the time, try it in one of those, see if you get a different reaction?

1) do you have all of your radios turned on? 2) did you set the radio mic switch to the right radio? 3) is the correct radio tuned to the correct frq? 4) do you get any audio return from your radio call to JTAC? ya see, if everything is set up right and you are just too far away, you'd hear fuzz or broken transmission, so your location is probably not the issue. If you have the radio on the wrong frq, the mic switch on the wrong radio, or even the radio not turned on, you will still get the radio menu, you can still get the JTAC menu and select the radio commands, and you still hear yourself say the statement. Only trouble is that you just said it to yourself, or to your wingman, or to AWACS... At first I could have sworn that JTAC didn't work, then I got a bit more experience, and now it seems to work wonderfully (with the exception that the poor guy can't prioritize the battlefield worth a darn).

no good deed goes unpunished... Thank you Nate for being open with your information!

Thank goodness this S#!T ain't easy, otherwise that feeling of success would not be nearly as satisfying

I look at it like "turning random failures on simulates real-world economics and/or an average crew" and "turning random failures off simulates a good ecomony, where maint. schedules are gospel, and the crew is totally on top of it". nice feature, but for that one night per week i can spare to fly in squad, i don't want to piss around with 'real world'.

I recently upgraded my whole system and chose a 560ti for my only gfx card. I'm happy with the 560ti, not sure if I could be pulling more fps with a more expensive card. Settings all on full, HDR on, AA at x16q, (push campaign missions) I pull around 60 most of the time. When spooled up and ready for take off, if I look forward I get 50-60, when I turn my head to look at the wingie sitting to my right it drops to 30-40. In air, I don't think it has dropped below 40 at all, most times it's pinned at 60. In the heat of a maneuver, in the middle of the action, it's normally in the 40's. I think I can say that AS filtering makes a difference; gazing at wide-open spaces seems to drop a few FPS at 16, the drop isn't so noticable at 4. So, I find the 560ti to provide a very playable A-10. I don't know if you get more from a 570, but I didn't think the extra $100 would get much. One weird thing, the 560ti seems to be one of the few cards that is not compatible with the nVidia advanced tools. Specs say it works for 550, 570, 580, etc... have not even tried to install it