Jump to content

All Activity

This stream auto-updates

  1. Past hour
  2. Attach your DCS log file in case it highlights any issues. I'd also recommend using https://github.com/fredemmott/XRFrameTools vs. fpsVR to test this out. You can export the results to a CSV file and then for the frame timings it will show other things happening at the same time which may identify the cause of the increase in those.
  3. Hallo zusammen . Hat sich seit den letzten UP Dates etwas beim Cold/Dark Start vom AH 64 geändert ? Gibt es dazu neue Listen zu runterladen ? Mein Promblem ist , das ich nach dem hochfahren der Engine , die George KI nicht einschalten kann ( z.B. mit STRG V ). Siehe Screenshot Da steht nur " READY SYSTEMS " . Das gleiche Problem habe ich auch auf den Servern .
  4. You referring to using the Custom option for example in the PimaxPlay software? Have you tried the solution posted here, a lot of people prefer Mbucchia's Quad-Views-Foveated, and using Tallymouse companion app to configure the multipliers and focal areas. Note that you don't have to switch to using Mbucchia's Pimax OpenXR runtime for this and can continue to use PimaxPlay as the runtime, just ensure you disable Quad Views in PimaxPlay if doing so.
  5. Radar cross section is not affected by whether your radar is on or off. However I think your radar can be detected by enemy airplane RWR systems, and that will alert them to your presence. I'm not sure if ground targets can pick up your radar emissions though; I suspect they can't. It would be interesting to do some empirical testing on this.
  6. I mean, is it modelled? Do you increase your chances to survive when sneaking through a high dense area of sam sites with your radar completely off? And how big is the difference in terms of cross section from SILENT to QUIET?
  7. Hi, I will ask the team to take a look in my morning. thank you
  8. Hi, please check Wags video are you sure you are not missing a step? Timestamped
  9. @Raven (Elysian Angel) Quote from EDs Announcment thread: "Our MiG-29A, NATO codename Fulcrum, will be the export modification of the “A” version that was supplied to Warsaw Pact countries." So "Fulcrum-A" might be the more appropriate term. In any case, I don´t see how that would negate anything that I stated.
  10. Чинук хоть и сырой в плане функционала, но даже в таком виде его оч приятно применять. Заценил вот автоматическое переключение с HSD на индикатор малых скоростей при выборе HSDH, на скоростях ниже 50 узлов. Удобно и то что на этой странице более наглядный индикатор вертикальной скорости.
  11. Thanks, but I am not in VR now and never had been
  12. Anyway, I have the same problem no matter which map and objectives I choose. George simply won't fire his onboard cannon anymore. This all happened after the last update.
  13. Hi I'm sure you know what IPD is, but for those that don't, it is the "interpupillary distance", i.e. the distance between the centres of your pupils. If you are trying to force 75mm or above, that seems very extreme. Most people are in the low 60mm range. Just a thought.
  14. Hi team, I am nearly 2 weeks into my new Crystal light upgrade from RIft S. I cannot get a setting to work. I have followed everyones online setup tips. I have tried native 72,90 and 120hz. I have tried all the quadviews and priority rendering on/off. I ideally would like 120hz locked to half, but if I try this on pimax play and/or in DCS the visuals are so blurry. Any variation of HZ halved is horrible. I can get a lovely clear image with 72hz and tweaking Quadviews and priority rendering, but lots of micro stutters ruin this. Smart smoothing helps a bit with this, but then seems to cause FPS to drop causing other problems. I have literally gone through every combo of setting with out a smooth clear experience. If i drop all the DCS in game settings to low, I get the same experience. I had online assistance with tech help the other night and they noticed from my logs that the headset had instances of not acknowledging settings from pimax play. We did some rectification by deleting logs and files and opening Pimax Play in admin mode. But none of this helped. And now to top it off the quadviews wont work at all. I select it on and can chose any of the 4 options, but the headset clearly isn't applying them. Tonight in the Pimax "space" scene I notice that if I turn my head left to right its stuttering very slightly. And if I focus on an object, I turn more than around 10 degrees, it goes out of focus. Now have a ticket open and am waiting further instruction.... I only use Pimax Play, no openxr or independent quad view. Is this the issue? Using lates version 1.0.18 firmware and Play version 1.42.1. System: Windows 11 Asus Z790 Nvidia RTX 4090 I7 14700K DDR5 64mb 6000Mt Drives are Samsung SSD 980 Pros
  15. There's one way not tied to the WinWIng software, few posts below there's also a WinWing software way
  16. I meant to be a little snarky, and maybe even a little self-deprecating as well, but it wasn't my intention to be an outright dick or make fun of you. My apologies for that. I thought only the French get offended when you don't speak their language? While I find it slightly inconvenient when I need a translator, I wasn't "offended" in any real sense of that word, nor did I view it as any breach of respect. I'm pretty sure the guy wasn't writing in Spanish to be a troll or piss anyone off, and he apologized for the inconvenience. It isn't a big deal, and everything is fine.
  17. Depending on the "Force IDP Distance" value in the VR settings, the helmet visor display shifts/deforms. The last value at which the visor covers both eyes in VR is about 75 for me. Anything higher doesn't work and shifts. It looks like the visor is centered only on the right eye. For example, the attached screen at a value of 100. I don't even know if this is a bug...? If so, please check. I assume that like the helmet sight, it is set to display in the right eye by default... maybe it will be necessary to set a default value for both eyes for its display? Selecting the display like in the case of the sight would not make sense...
  18. Any plans yet to add support for MiG-29A Fulcrum module in Simshaker for Aviators? How does it work for you? On my end it doesn't work (on final verson 2.9.0.0) What software version are you using?
  19. True but I consider that a mid service upgrade. But is is true that the German Planes are 9.12A's so i would be fine if later on down the road we might get it, but i don't think it's something we should really expect.
  20. That’s strange. HDR is working for me. can you redo the steps here https://forum.dcs.world/topic/356128-reshade-vr-enhancer-mod-vrem/page/15/#findComment-5696048 with HDR on and post files ?
  21. Not fixed in 2.9.20.15384. @BIGNEWY This core bug has persisted for 3 consecutive versions, so I presume it has flown under the radar.
  22. ... then you wouldn't call it "MiG-29A 9.12A" since that doesn't exist: an aircraft can't be 9.11 and 9.12A at the same time, especially since 9.11 never materialised and was just an idea abandoned in 1976
  23. Yes, this is my solution in response to player requests. Several people wrote to me that the ships are hard to find, and it would be nice to mark them with smoke. The eternal search for a happy medium between DCS veterans and newcomers.
  24. Not fixed in 2.9.20.15384. @BIGNEWY This core bug has persisted for 3 consecutive versions, so I presume it has flown under the radar.
  25. Forgive me. I was mistaken. I'm too busy working with the Outpost campaign series. I was trying to test this method and completely forgot that the MAD KA-50 doesn't have Russian voiceover. Sorry for misleading you. There are no Russian voiceovers here. https://www.digitalcombatsimulator.com/en/shop/campaigns/mad_black_shark_campaign/ https://store.steampowered.com/app/2635100/DCS_MAD_Black_Shark_Campaign_by_Stone_Sky/ I checked - it is indicated correctly. Russian voiceovers are only available in MAD, MAD JF-17.
  1. Load more activity
×
×
  • Create New...