Jump to content

Syd

Members
  • Posts

    35
  • Joined

  • Last visited

Everything posted by Syd

  1. I'm not sure what you mean by "adjusted temperature in-game". If you're thinking about temperature error on the altimeter than yes - once you set temp. other than 16C than you will see that your altimeter indication is different than your ASL. To be precise - in temps lower than 16C your altimeter shows higher than you actually are, and for greater than 16C it's the opposite. That is why IRL in really low temperatures you have to calculate this error for safety reasons (mainly during approach phase).
  2. Just a quick note on the temperature. From what I've checked, DCS's standard temperature is 16C. This is the value at which altimeter temperature error doesn't occur (at least to a certain altitude). 20C is nothing more than default ME setting.
  3. @Capt. Winters Hi, I don't know if you solved your problem but solely disabling antivir/firewall in ZoneAlarm didn't work for me. Adding DCS in the excepsions didn't work either. In the end I had to uninstall Zone Alarm alltogether and DCS started working.
  4. I'm using ZoneAlarm and tried turning off both antivirus and firewall in control window but it didn't help. Only full uninstall fixed the problem. Afterwards I reinstalled ZA and DCS still works fine.
  5. You were right - antivirus was the problem. I couldn't find how to add exceptions so decided to uninstall it all together and DCS works fine. Thanks for your help.
  6. Same. Maybe fix on the 23rd will help.
  7. Here it is. But I don't think this error generates any logs since after I try to launch none of the files in the folder change their date of modification. dcs.log.old
  8. Here you go. That was generated few minutes ago during the launch of the previous version. Then I updated to the latest one and the error popped up as usual. Finally I copied it here. I think nothing changes in it after the unsuccessful start up. I even tried removing it before the error but no newer file was generated instead. dcs.log
  9. After DCS 2.5.6.59398 update I am unable to start DCS. After I click DCS.exe the first window pops up (update check I think), fills up the bar, disappeares and a window with "Procedure entry point could not be located" shows up. The bottom description of this window is a path to DCS.exe file. Everything is fine when I revert to previous versions. Did a fresh install, cleaning and repair options. Nothing works.
  10. Recently I've been looking into how realistic the weather system is in DCS in relation to barometric altimeter indications - "not great not terrible" as one would say. First, I was checking ISA athmosphere and for some reason ED decided to use 16 Celcius degrees instead of 15 as standard temperature. Not a big problem there. Once you set 16*C and 29.92 everything is as it should be - baro alt equals your amsl alt at all time. Then I looked into altimeter temperature error that occurs in different than standard temperatures (16*C in DCS). It is modelled, only real world equations don't apply. I think ED even modelled stratosphere layer since error is getting bigger above 35000ish ft. Lastly I decided to check how changing QNH setting influences altimeter. And here's my problem. If I'm correct, while temp is standard (16*C) then once you set altimeter to your mission QNH setting, indications of baro alt and AMSL should always match. But they don't. There is some strange error that occurs, similar to the temperature one (the higher you are the bigger it gets). I don't have a lot of modules but from what I saw it happens in F16 and F18 (that's why I'm posting it here). A10 for example does this right. Temperature error I mentioned above looks/behaves the same in all my official modules. I know QNH/pressure system in DCS is deeply flawed from the start (QNH shouldn't be called that for start, since it goes out the window once the temperature is different than 16*C) but this is a really strange behaviour. I get that DCS is not FS/X-Plane but is dev team aware of that error? Or maybe I'm wrong and it should be like that?
      • 2
      • Thanks
×
×
  • Create New...