跳转到帖子

Lee1

Members
  • 帖子数

    233
  • 注册日期

  • 上次访问

最新回复 发布由 Lee1

  1. Thanks kksnowbear,

    Definitely got a 1000w PSU.

    Intel Core I9 14900k, Raptor Lake

    MAG Z790 Tomahawk Max Wifi, Chipset Intel Raptor Lake, Southbridge Intel Z790

    Corsair 64Gb DDR5, 3000mhz (2x32Gb)

    Nvidia 4090 graphics card.

     

    Hope that helps.

     

    thanks

     

     

  2. Help please community.

    Most times I try and fly DCS (F16) my screen goes black and the fans on the PC go to maximum very shortly after starting a flight. Doesn't always happen, I managed to fly the complete free flight Kola mission yesterday and several approaches at the end with no problem whatsoever. Using Logitech X56 Hotas.

    Sometimes the computer wont start at all, just giving me a black screen even though the PC stack is humming away normally. I swapped the DP plug from the graphics card output and put it in the motherboard and it worked, but woefully slow for flying as I expected. I don't suspect DCS because it randomly does it at other times too, but usually very quckly when it's working hard on DCS. As I said, sometimes it goes very well for a whole flight. Is it possible that all the recent updates have caused a problem in DCS itself? There have been a LOT of huge updates.

    Corsair iCue won't run and I get a message on the iCue app saying that and Corsair's own advice on how to fix it doesn't work either. It says to do an update, which it won't do because it says there is something already in the folder (well, dohhh of course there is) and it will not let me uninstall it and is just "greyed out" on my uninstaller. So, possibly spurious temperature readout causing prog crash and fans to go to max? Who knows, I don't?

    I checked the Device Manager at one point and it said that windows had detected a problem and turned off the graphics card (Nvidia 4090). I had not seen that before or after any subsequent failure. I suspect the graphics card but not tech savvy enough to prove it.

    It started about the end of November and the computer is currently less than six months old.

    Any ideas please? Any help would be greatly appreciated.

    I'm taking it back to the builder this week but any heads up would be appreciated.

    Many thanks,

    Lee

     

  3. I git a new computer as my old one wasn't coping at all with all the improvements over the last year or so.

    I have everything bound properly on my Logitech X56 Rhino but the mini (Thumb) joystick on either the throttle or stick will not do anything at all in the Axis commands.  I have been told there may be problems with the X56 recently. Please can you tell me if this is a bug and being worked on?

    Thanks

  4. I've got a new computer because all the new improvements made over the last year or so totally overwhelmed my old one.  I had everything nicely mapped on my Logitech X56 Rhino Hotas.  I've got most things back where they belong, but for the life of me, I can't find how to bind the mini joystick to slew the TGP etc. ISTR it was an axis command but I've tried that and it doesn't seem to give me the option.

    Please can one of our experts tell me where I'm going wrong, what I might have missed and how to fix it?

    Thanks in anticipation.

    Rgds to all

    Lee

     

  5. 59 minutes ago, LucShep said:


    If I understood correctly, you're not using VR.  If so, no need to buy the latest and greatest, though the most potent machine for your budget is obviously the best idea.

    But we need more info to recommend or advise hardware...

    1. What are your current system specs?
    2. What is your total budget (rough estimation)?
    3. What is your screen (native) resolution?
    4. What DCS modules+maps you intend to use?
    5. Are you computer savvy, i.e, will you be building the system yourself? 

     

    Thanks for the reply

    Current system not relevant, mI'm looking for a new one but  Intel I7 @3.4Ghz, DDR3 24Gb RAM, Gigabyte Z68XP-UD3P Board,NVIDIA GTX 1070.  As I said, old and creaking.

    Budget no more than five thousand pounds

    Currently 3440 x 1440 but monitor can go higher, limited by current system

    Persian Gulf, Syria, Afghanistan, Kola Peninsula, Caucasus, NTTR, also have Marianas and South Atlantic but not currently installed

    Not building myself, a local guy is doing so and I have had his products before, top notch.

     

    Thanks again for your interest and help.

     

  6. I've come to the point where my present computer is not performing well enough to run DCS with all the improvements made. For instance, it takes several seconds to roll the F16 through 90 degrees, the program keeps stopping for a couple of seconds to catch up, stutters along and most of all takes about ten minutes to load DCS and a similar time to load up whatever option I've chosen to ly.

    I'm able to spend a fair bit of money to rectify this.  I want to be able to fly with all the sliders fullt to the right, ie maximum fidelity, but don't rteuire VR headset capable.

    What are you guys using and what could you advise.

     

    Thanks in advance.

     

    Rgds

     

    Lee

  7. On 6/26/2024 at 10:10 PM, draconus said:

    It's 26th June, does it answer your question?

    Thank you so much for your helpful contribution.

    1 hour ago, Boosterdog said:

    Ask ED for a refund for the SW region map.

    See the FAQ. The Full map you bought already includes the SW region as well as the other 2 planned regions when they are released. 

    You can only use the SW regaion right now as thats the only part so far released. 

     

     

  8. Hi Folks.

    I have a significant birthday coming up and my lady wishes to buy me something really nice to mark it. I currently have a Rhino X56 Hotas set up. I'm having difficulty with the very fine control required to do AAR in anything i fly. Is it plain hamfistedness on my part or is there a better setup I can get to facilitate this annoying inability to accomplish AAR?

    Thanks and regards

     

    Lee

  9. 5 hours ago, Lace said:

    I didn't say it is the same, I said it is often the same - obviously it depends on local weather conditions, but it is generally within one or two mb of your departure field, because that is the pressure setting for that region.  Over longer distances it can diverge further from your initial setting, but your final setting should again be quite close to your arrival QNH.

    I'm not sure where you fly, but in the UK we don't use quadrantals, it is a semi-circular rule for VFR deconfliction, with 000-179MTrack being odd+500, and 180-359 even+500.  However, IME most people don't use it and compliance is not mandatory.

    I'm sure some readers might find this interesting, but we are drifting well away from the OP question now.

    🙂 I stand corrected!

     

  10. On 6/25/2023 at 9:45 AM, Lace said:

    QFE is mostly for circuit work or visual rejoins, and as razor correctly states, will read zero on the ground, and your height above the airfield when in the air.  As a result it is only really of any value in the immediate vicinity of the airfield.  The jets modelled in DCS mostly have a RADAR altimeter, which will only read height (not altitude), and therefore is the primary reference for low-level flight.   QNH will read your altitude above MSL.  Each airfield will have an elevation value from a datum point (which may or may not be where you are parked).  With QNH set your altimeter should read the same as the airfield elevation.  QNH is usually the same as the Regional Pressure Setting, and will give you an accurate altitude over a greater area of land.  On a low level cross-country flight you will receive several RPS en-route and will adjust your altimeter accordingly (if you didn't adjust and were flying towards an area of low pressure, then your altimeter would begin to overread, i.e. you would be lower than you think - which could lead to CFIT).  For high level flying, once you cross the transition altitude (varies by country, USA 18000 ft, UK much lower at around 3000ft - we don't have any high mountains) you will set 1013mb.  This will ensure all aircraft are at the correct Flight Level.  At these heights it is more important to harmonise traffic than to know your exact altitude above MSL.  With everyone working with the same std pressure setting, then deconfliction is made easier.  FL is reported in 100s of feet, so FL300 is 30,000ft.

    The issue with some of the Sinai map, is that some of it is below MSL, which makes accurate altimeter setting difficult (or impossible).  However, as stated, use your RADALT for low down work, and a standard pressure setting for high level and you'll be fine.

    QNH is not the same as RPS. QNH and RPS can be different and usually are in my experience. The QNH as you rightly state is where the altimeter reads the airfield altitude AMSL when sat on the airfield. RPS is the setting one would use whilst poling along low level but outside the airfield environs so that everyone flying around VFR iis using the same pressure setting when not relying on Radalt and is a forecast for the whole area. Makes life easier when GA traffic is flying around using quadrantals! Don't imagine the military stuff these days has much use for RPS anymore what with either flying around high level to get somewhere economically or else tearing around low level and just looking outside making sure not to hit the ground or antyhing in the air 🙂  Transition level as you correctly say is when one changes from QFE/QNH/RPS to the standard setting 1013mb/29.92inches.

  11. Loved it so far.HAven't tried any of the weapon systems as yet, but I have no problems flying it generally and around the circuit using the units of AOA for circuit work and landing. Good module and I expect it will only get better as did the F16.

    • Like 2
×
×
  • 创建新的...