Jump to content

drPhibes

Members
  • Posts

    1182
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by drPhibes

  1. That list is over 5 years old. This is the most up to date info from Razbam: https://forums.eagle.ru/showpost.php?p=3060848&postcount=1
  2. Nice video! Did anyone else notice that the wheel gauge of the trains and the track gauge doesn't match? Perhaps the track texture is based on standard gauge (1435mm/4ft 8.5"), while the VL-10 and ChME3 locomotives are russian gauge (1520mm)? I guess I'll have to set the year in the mission editor to 1945 and check if the DRG class 86 matches the rail gauge (setting the year to some time in the "steam era" actually replaces the modern(-ish) comblock rolling stock with steam locomotives, if you have the WW2 asset pack).
  3. The flashing stops after changing the code (when airborne). The fault does not reappear after subsequent rearm and refuel cycles; it only happens the first time the TPOD is added.
  4. Have you tried googling "qfe to qnh conversion"? The first hit (stackexchange) explains it pretty well. As long as you are able to find the airfield elevation and have a calculator (for dividing by 30 or 900), the conversion is pretty straight forward.
  5. Not a good idea unless you check with ED and get permission. Asking for donations for DCS-related work is a violation of the EULA, and it could get you kicked off the forums if you're unlucky. Nobody wants that to happen.
  6. You can toggle between the wide and narrow field of view using sensor select left in HTS mode (double click sensor select down to switch from TPD to HTS). Unfortunately, the regular zoom is not controllable from the HOTAS unless you map the relevant MPCD buttons to buttons on your stick (and this will ofcourse mean that these butons have a different function in other MPCD modes)
  7. If you start a mission with the pod and GBUs loaded you can use the pre-set 1111 code, but if you add the pod and bombs through the rearm&refuel dialog, you need to change the code to something (otherwise 1111 will just keep flashing, like when you are on the ground).
  8. I have had some trouble with the auto hover lately (it was impossible to engage it with the assigned keyboard and joystick inputs, even though the ground speed was close to zero, and the vertical velocity and bank angle was within spec), but re-doing all my SA342 control assignments fixed it.
  9. Same here. I Spent most of the day yesterday lasing and dropping GBU-12s, so it definitely works. Try running a repair using the dcs_updater application.
  10. Not all of them. The ЧМЭ3s are diesel powered.
  11. I never really considered buying CA, but this video (and general fooling around at treetop level in 2.5) convinced me. And I finally got to spend some of my bonus points, so it cost me just 6$ :)
  12. Green is a color. Joking aside, the displays are capable of displaying other colors, but green is used in the AV-8 for NVG compatibility.
  13. Some low altitude fun in the AV-8:
  14. I started DCS and logged on to the AO server (with 30-ish players). The total memory use increased by approximately 14GB, but the DCS process only used 7GB. The remaining 7 was nowhere to be found in the task manager, so it seems like there is a memory leak somewhere.
  15. ...and DOOM3 doesn't run on my computer that used to run DOOM II flawlessly. It's almost as if hardware requirements change as games evolve. Who'd have thunk it?
  16. 2.5 looks fantastic. Thanks a lot to the whole ED team :) Keep up the good work!
  17. The OT just wrote "Aust", so the release time depends on whether you use the "-ria" or "-ralia" suffix.
  18. Updates usually go live around 16-18:00 CET
  19. It sounds like you are too far away from the tanker. You need to be pretty close in order to get a "cleared contact" message.
  20. drPhibes

    52B?

  21. And instead of the "hey, what are you doing?" when we forget that the ground crew are still doing something, we could have a loud bang with a subsequent engine failure caused by ingesting one of the ground crew. Or am I the only one with a pretty morbid sense of humor?
  22. You probably forgot to save the file with the alpha channel that defines transparency (i.e. the actual shape of the numbers).
  23. A/A TACAN using only the onboard interrogator can only give the distance. For bearing information, you need a full TACAN beacon/transponder, which is too bulky for integration in a fighter (and not really needed).
  24. Sorry guys, but you'll have to wait for another week:
  25. This seems to be the cubanace modus operandi. New "projects" announced every other week, which are usually cancelled after a few weeks, with every trace of them being deleted from the FB page (to mention a few: F-16, Mitsubishi F-2, Northrop YF-23, Su-17, Mig-23). A five second attention span is not the best starting point when trying to learn 3ds and c++/lua coding at the same time...
×
×
  • Create New...