Jump to content

All Activity

This stream auto-updates

  1. Past hour
  2. Sorry, I can only hope that Ugra leaves it as it is. For the eastern German part of the country and the Soviet bases, it fits very well. After all, they were the complete opposite of clean and tidy. Okay, one could argue about the many small ground cover plants and the 1-meter killer grass, but sand, dirt, scars in the grass, and wild paths were absolutely omnipresent.
  3. Yeah, I have just given in and depopulated the deck before I fly the mission and save it as update. Painful to have to do that but it's not the first time I have had to make changes to missions because of an update. Part of life in DCS!
  4. @Silhou Hey there, This problem still exists, almost 2 years after this post was made. It is very, very frustrating for our Carrier Air Wing, significantly delaying missions because of people having to takeoff, find out they have the bug, quit DCS, rejoin, restart the jet and try again. It really takes a lot of fun out of taking an F-14 from the boat (where it belongs) in MP. Hope you guys can find something.
  5. I will wait. My machine went from running dcs crash free to randomly crashing right after the patch. I know about the log analyzer advice and have been following it for months. I don’t run mods.
  6. Read about your interest in the mechanization for an air to ground variant for the R-60.  Feel your pain in that I tried to get a similar conversation going about adding a seeker slew joystick for the OH-58D AHIP as what finally made the Kiowa Warrior compatible with the Air to Air escort mission for Apaches when MLMS became ATAS.

    Got the post stripped from the forum and every subsequent message to which I replied with public data here denied as well.

    These people are serious about anything related to tactics or operational use being 'not suitable for DCS', a tactical military sim.  It would be hilarious if it wasn't so sad as these are the people repressing DCS development at every turn and with War Thunder in particular moving to advanced inertial-active missile defeat and MSI level sensor fusion, such backwards thinking is going to destroy the sim, if it hasn't already.

    Anyway, I recalled coming across a post on the Secret Projects UK forum titled:

    'molniya-vympel-r-60-aa-8-aphid-aam-variants'.

    And noticed a few things regarding proximity vs. induction fusing  and the use of various add-on features in subsequent Izdeliye product variants of the R-60 which included one mentioning an Ataka radio command link.  You should look it up.  The Aphid was a genuinely innovative design for it's time, as much a replacement for cannons as a competitor/complement to the R-13 and subsequent, 'dogfight', weapons and as such, it went through a lot of updates from enhanced digital autopilot to wider IFOV and OBS limits to cooling and target designation upgrades, allowing for faster handoff.

    It's 5` IFOV in particular interested me as this is rather a wide squint for a seeker intended to reject IR expendables and yet, for a large diffuse target without mechanical IRCM, it would likely be a considerable aid, given only that you could command guide the missile to a distance (under EO control from the Hind optronics) to where that was the only dirt/pavement/burning building object in the FOV.

    So...  Launch on digital autopilot, steer a smooth trajectory to the point at which seeker lock-on is assured, handoff to the weapon and watch it slam into a contact vs. proximity fuse detonation in a cluttered ground environment?

    Not saying I have your answer, but it might be worth looking into.  Lots of genuinely more technically knowledgeable people on SPROJ as well, though they do not always open up honestly, which is understandable, given the subject matter.

    Good Luck.

  7. It's probably somewhere already on the Forum, but I was having a problem saving my TrackIR profile changes - specifically the Motion Control slider, as well as linking the profile to DCS in the games pulldown window. Searching online I found the solution was to just run TrackIR as Program Administrator (right click when starting it), then make the changes and save.
  8. Это во всяких Pico и Quest так только, наверное. Страхов чего? Настройки? Надо смотреть, что именно за шлем. Если того, что могут быть проблемы даже на топовом железе, то это к ED вопросы. Более убогий Ил-2 работает стабильно в VR даже по сети.
  9. I think I still can fly it. Try to remove the whole mod from the Saved Games directory and start installing from scratch. I some how cannot attach a screenshot here
  10. This is incorrect. The "Relative Wind" direction shown in the bottom left appears to be calculated at mission start? and won't necessarily be the metrological to/from direction i.e. the OP's mission has a 12 kts wind towards 188°T, yet the Airboss screen shows the direction as 242°
  11. Not many votes? I think this post needs to be shared where people can see it.
  12. Correct, with this subject no changes. I hope that they work on the fix.
  13. So….found floodlights…but they don’t actually omit any light in daylight conditions…there’s also a “lighthouse…but it only has a very faint white patch on it..I wouldn’t call it a beacon. found a unrealistic work around..under “Effects””Big Blue Smoke” and then you can preset to smoke or smoke with fire and 3 sizes to choose from. I know DCS is revamping the ATC system,Hopefully they will figure out a solution to let us turn on runway/carrier lights in low visibility situations.
  14. Same here. Even after reinstalling aircraft avionics I cannot get into cockpit anymore and control it.
  15. Today
  16. People are overthinking the math on the angle of wind. "No crosswind" means natural wind straight down the angled deck's axis. That's it. As long as the carrier is moving there will be axial winds going from right-to-left. This is normal, and is not meant to be canceled out by any fancy math like that calculator on github (or even the airboss script). In fact at lower natural wind speeds those calculators will totally f--k up your groove turn. There are axial wind (crosswind relative the angled deck) allowances up to 7kts, but under normal operations natural wind goes straight down the angled deck[1][2][3] As to the rest, here you can see the headings on the Airboss displays appear to be True, not Magnetic. Wind is showing as "to" instead of "from," like in the mission editor wind settings. I suspect this is an error as Western convention for wind is always "from" regardless of aviation or simple civil meteorology. If the mission wind changes and it is not reflected in the briefing, then note the "wind bearing," find the reciprocal, add 9. That is the bearing you must set the carrier for recoveries. The "crosswind" display appears to be crosswind relative to BRC, not to the angled deck, though I need to test again to be sure. Depending on natural wind speed you will have a crosswind indicated on that display due to the axial winds caused by the ship's movement, but those should be less than 7kts. [1] CNATRA P-1211 [2] The Burble Effect: Superstructure and Flight Deck Effects on Carrier Air Wake [3] Aircraft Carrier Operating Procedures For DCS World 2.5 (which uses CNATRA and NATOPS sources)
  17. What's the mission you're attempting this Mach 2 run in? The weather/atmospheric conditions do play a part in the maximum speed that you can achieve. I'm able to achieve Mach 2+ in level flight at 38000ft with a standard day.
  18. @Nightstorm after the latest DCS patch, the mod stopped working. I tried re-applying avionics mod but it doesn't work. What should I do now ?
  19. Do you have exactly the same problem as this post and log errors? You probably shouldn’t hijack old posts. If you have an issue then raise a new post and attach your logs. You don’t need to install DCS again. Just remove any mods and run a slow repair of the game.
  20. People’s DCS can crash to desktop for numerous reasons. If Windows is killing the process then it may be machine specific and something wrong with your PC. In which case there may not be a game fix. Run the Windows DxDiag tool, save the report, and attach it here as well. The log analyzer also had more items than the ones you listed there, eg turning off SSAO and SSLR, setting shadows to medium, etc. It also shows you have a custom mod. Have you removed all these mods, run a slow repair of the game, and deleted your Saved Games\DCS\fxo and metashaders2 folders as well?
  21. For openxr, capframex, RTSS, presentmon and others may be easier, but the numbers they give are wrong, and they can actively harm the VR experience because they work on the “send to mirror window” part of the game, not the VR part. https://github.com/fredemmott/xrframetools?tab=readme-ov-file#why-should-i-use-this-instead-of-my-favorite-tool-for-non-vr-games If you go beyond monitoring with these into framerate limiting, vsync, or other modifications, these will either do nothing to VR beyond placebo, or tie your headset to your monitor's timing rather than the runtime's timing, often leading to stutters, motion misprediction, and other tracking issues. Edit: for example, accurate support for OpenXR has been an open feature request for CapFrameX for over a year: https://github.com/CXWorld/CapFrameX/issues/277 While Google's AI and a guest post on Pimax's blog say PresentMon support OpenXR, this is incorrect. This is obvious from the fact that it does not have an API layer. The only other way it could provide accurate numbers would be if it integrated with the runtimes - given PresentMon itself is open source, it would be an unusual choice for them to integrate with some runtimes, but none of the open source ones (like VDXR) - and another bad choice to display incorrect information on other runtimes rather than a 'runtime not supported' message which woudl require an API layer. PresentMon can hint about your load, but this says nothing about timings/bottlenecks unless something is at 100%. I'm also not seeing any trace of OpenXR-related code in PresentMon's source code.
  22. There are a lot of bugs after EFM update. Good luck
  23. Second try early this morning, straight level fligh, clean configuration, A40 full burners = impossible to reach Mach 2. Please could someone tell me if you have the same "problem"? thx ps: In the Mirage F1 no problem at all to reach Mach with the same parameters.
  24. I've given up hope that Ugra will ever fix this massive error. We've told them ever since they showed the first previews that Germany does not look like this. They never acknowledged the issue even once. The topic has come up again and again, only to be met with silence. So thank you for your efforts with this new topic, appreciated!
  25. In the CC manual is explained.. the gunsight has 2 options.. fixed and gyroscopic (AUTO). AUTO mode tries to give you a kinda CCIP solution.. works fine with the guns..not so with everything else.. for droping stuff or using rockets is prefered to set it to manual and set depresion MILS acording to bombing /rocket tables.. It also works in air to air in AUTO .. both as a gyro stabilized gunsight and also as the piper for the IR seeker.. you can even set a range so you know where a 35f wingspan target would be in range aligned with the sight if fits between the sight marks
  1. Load more activity
×
×
  • Create New...