Jump to content

Bearfoot

Members
  • Posts

    1628
  • Joined

  • Last visited

Everything posted by Bearfoot

  1. But does the phrase not suggest that the first pair goes in A1 and A2 (i.e. channel A), and the second pair in B1 and B2 (i.e., channel B)?
  2. Hi Demon_! Thanks ... but then why does the text say "You may install varying memory sizes in Channel A and Channel B", which implies A(1+2) forming one channel and B(1+2) forming the other? Or is the pairing of RAM different from the pairing of channels?
  3. Ah, yes, RTFM! Ok, here is the relevant page: The next page of the manual says, """ You may install varying memory sizes in Channel A and Channel B. The system maps the total size of the lower-sized channel for the dual-channel con guration. Any excess memory from the higher-sized channel is then mapped for single-channel operation. """ It seems that the first two slots are one channel, "A", and the next two are the other channel, "B"? Am I reading that correctly? If so, then in my case, each pair of different color slots forms a channel pair, and I should go for the AABB configuration? Or am I reading that wrongly, and it "1" and "2" are the two channels, and "A" and "B" are the sequence, in which case I should be going for the "ABAB" configuration?
  4. The Bf-109 F4 Trop, of course, the ride of Hans-Joachim Marseille. As well as some Bf-110's, Ju-88's, and Ju-87's. And some Hurricanes, Warhawks, Kittyhawks, B-25's, and B-24's. j/k ... sorta ... but not j/k really. Would love to see these in a desert conflict setting ...
  5. With respect to making sure matched pairs in a dual channel, I have 4 memory slots, counter-shaded tan, dark, tan, dark, as can be seen here: https://www.asus.com/us/site/motherboards/Z97/assets/img/thumbs/enlarge/sabertooth-z97-1.jpg I assume that the adjacent tan + dark are a matched channel? Or is tan + tan one matched channel and dark + dark the other matched channel? So, if I have 2 sticks of Type "A" and two sticks of Type "B", should I put them in as: AABB or ABAB ? Right now, they are in: "AA__" configuration. The leftmost stick is touching my CPU fan box :(
  6. Thanks again Demon_! I've just ordered this: https://www.newegg.com/Product/Product.aspx?Item=N82E16820233278
  7. On my Z97 Sabertooth motherboard, I currently have the following memory modules: CORSAIR Vengeance Pro 16GB (2 x 8GB) 240-Pin DDR3 SDRAM DDR3 1866 Desktop Memory Model CMY16GX3M2A1866C9R I want to add some more memory, but cannot find the above make/model anywhere. Is it OK if I add one of the following to the system alongside the above? Ballistix Sport XT 8GB Single DDR3 1866 MT/s (PC3-14900) CL10 @1.5V UDIMM 240-Pin Memory Module BLS8G3D18ADS3 https://www.amazon.com/Ballistix-PC3-14900-240-Pin-Memory-BLS2C8G3D18ADS3/dp/B00D9QFSUE CORSAIR Vengeance 16GB (2 x 8GB) 240-Pin DDR3 SDRAM DDR3 1866 (PC3 15000) Desktop Memory Model CMZ16GX3M2A1866C10 https://www.newegg.com/Product/Product.aspx?Item=N82E16820233278 16GB Module DDR3 1866MHz PC3-14900 / PC3-15000 240-pin DIMM 1.5V CL10 PC Desktop Memory https://www.newegg.com/Product/Product.aspx?Item=9SIA7S65619004 Otherwise, would you be able to suggest some alternative options? Any advice/help appreciated! Thanks!
  8. How is this book? Is it heavy on the "smell the cordite and feel the G's, push this button and pull the stick" sort of detail? Lots of descriptions of air combat maneuvers etc.? Details on life as a Soviet pilot in Korea, or the general conditions (barracks, personnel, etc.) of Korea? Propaganda?
  9. So, I broke down and got the Mig-15. My impressions, compared to the F-86: (1) A lot more tricky and a lot less forgiving to fly well in combat. You have to keep your speed within a particular window to maintain performance/control. Too slow and you become sluggish, or, worse, stall/spin. Too high and it becomes very difficult to control. This speed window is not only small, but is easily exceeded even in normal (straight and level) flight. On the other end, it does not take extreme turns to drop below the window either. The F-86, by contrast, is a lot more forgiving easier for a bad pilot to fly: no real upper limit on speed window (except maybe powered dive?). And not only do you really, really, really have to overdo the turn to lose speed enough to stall, but: (a) you maintain full control of the aircraft until that point (no real degradation of performance); (b) you have lots of warning before things get out of control; and © it is easier to regain control. (2) An absolute beast of a climber! As advertised! (3) Some sort of je ne sais quoi cachet to it! This one is subjective, but there is something about that stubby silver cigar with arrowhead swept-back wings that is very, very, very, very, very, very alluring. Simple, tough, not brutish by any means but neither would anyone call it elegant. Weird that I don't (right now) feel the same "romance" for the F-86 because they look very similar, but there is a rustic/historic/nostalgic charm about the Mig-15 that makes me want to fly it over the F-86 regardless of the comparative performance pros and cons!
  10. Wut? Your shipping notification already?!
  11. Wonderful!! Looking forward to it!
  12. I will leave mickt to confirm/deny himself, but it seems you are either misreading what he says or I am misreading you. Mickt was not saying the the Gazelle is an arcade simulation or that he wants an arcade simulation. He was saying that people who use the simulation go out of their way to induce or otherwise obsess about fringe aspects of the flight regime such VRS etc. are using the simulator like an arcade game and thus might as well as go for an arcade game, as, in real life, not only are VRS etc. never directly sought out but is so rare that he himself has never encountered VRS in all his years of flying. We all want authentic high-fidelity helo simulations, otherwise we would not be here ... Just my 2c
  13. The Oculus Debug Tool? This does not seem to to be the case. E.g., I can set PD of 1.5 in the tool. Restart the Oculus service. Then quit the tool. Then even reboot if I feel like it. Then start DCS without starting the tool (or Oculus Tray Tool), and get the PD of 1.5 (cross-checked by independently launching Oculus Tray Tool if I set the PD using the Oculus Debug Tool or vice versa). That is, it seems to "take" once set, whether or not the tool is subsequently active. EDIT: Now that I think about it, I think use the Oculus Tray Tool to set the PD above, not the the debug tool. And that setting definitely persists through multiple reboot cycles, without the tray tool needing to be subsequently active. Need to check if the same holds for the debug tool alone.
  14. It was not a double post --- the post contents are different.
  15. When experimenting, I typically cross-check. E.g., use Oculus Tray Tool to set PD to 1.5, restart the service, then launch Oculus Debug Tool to confirm that sampling shows 1.5. Or vice versa. Regardless, DCS should be launch last -- i.e., after all the fixin's and mixin's and service startin's and restartin's ...
  16. Nobody cares to comment? Not asking for a timeline for a fix, but just whether this is even on the radar/to-do list, or is something that is not going to be addressed any time soon ..
  17. First off, GREEEEEEEEAAAAAAAAT module! Thanks! Now, I know, this is a known issue: the distorted/wavy gunsight in Oculus Rift. And a known cause: ASW/ATW. And a known "solution": disable ASW/ATW (CTRL + NumPad1). What I would like to know is that whether the developers are planning on fixing this on their end, so that we can fly the spit with ASW and still have a proper gunsight? I get that the issue is the FPS not being sufficient, so ASW is kicking in and causing the waves. And so, in a sense, there is no problem to fix from the developer's perspective ... except that this issue only occurs with the Spitfire module (for me and many other folk), and occurs even if there is not much else going on (e.g., the free flight instant action). So something in the core module is eating up a lot of processing power making sending those frames to the VR system very problematic. Do the developers have plans to optimize or improve the code to fix this? Or are we stuck with disabling ASW/ATW (which sucks, because then we get stutters instead of smoothness, and that makes for a horrible experience)? Thanks!
  18. Tray tool wraps the command-line debug tool with a GUI, and adds facility to control some other things, e.g. your USB power management. But largely the same. So, either/or.
  19. Would somebody who has this be so kind so as to measure the base dimensions? I've seen this listed on Amazon and elsewhere, but it is not clear to me whether the reported figures are length/height/width of the base including or not including the levers. I am particularly interested in the area that will be taken up by the base. Thankss!
  20. This is awesome!!! Thank you!!!
  21. So, the countdown begins (again)! Anyone know China-US DHL shipping times??? :)
×
×
  • Create New...