Jump to content

Mobius_cz

Members
  • Posts

    196
  • Joined

  • Last visited

  • Days Won

    1

1 Follower

About Mobius_cz

  • Birthday 05/02/1990

Personal Information

  • Flight Simulators
    IL2 series, DCS, FSX
  • Location
    Czech republic
  • Interests
    Planes, music, fantay and sci-fi literature

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hey guys i will share my experience I have RTX 3070 and Quest 2. I had two models in my mind to choose from. AMD Sapphire RX 7900 XTX Nitro + or Nvidia Gigabyte RTX 4080 Gaming OC. I really did some research with those cards and find out that AMD might have problems with VR but i gave it a try and bought AMD card. Raw performance in 2D in 1440p was excelent. My setup is with Ryzen 9 5900X and with this card i had power consuption (from the wall) at 630W during 3D Mark test. Everything was superb until i turned on my Quest 2....Don't get me wrong this card is still a beast and for non VR users it is a blast really. In DCS i had 90FPS in solo A10C free flight with MSAA 2X, textures on HIGH and Quest resolution in PC app bumped up to 5408x2736. And there are two reasons why i am sending this GPU back to the store. 1. Via Air link i had noticeable distortion on right lens. It was like when you try to see anything through glass bottle full of water. The problem disappeared while using cable link Quest to PC. I can use cable with DCS with no problem but for the other games it is issue because i don't have enough space around PC for normal VR stuff and i am payingVR games maybe 5 meters from PC. I tried to uninstall whole Oculus App and it helped..for the first Air link connect and then i had my fish eye back. My guess.. it is not AMD fault but somewhere between AMD and Meta because reinstall worked without touching of AMD settings at all. 2. And the second reason.. i don't know why but text and textures looked sharper with RTX (just my opinion form direct compare). Maybe coding/decoding, different compression? This might be just bad setting somewhere so bear with me And probably it is connect only to Quest 2 because no direct HDMI or Display port connection. If you like AMD products give it a try. But be prepared to encouter some difficulties with VR, i hope those issues will be solved in the near future but i need something what works for me right now Cheers
  2. Hi, i had same issue. You need to switch transformers mode 115V and 36V to "main" i think it is right click, they are located on the eletrical panel with generators. Step 32 in manual. And yes, this is not shown in the video from Wags afaik.
  3. Yeah i can also only speaks about what i have seen. Cockpit in that particilar Mi35 was in black color. I also got chance to sit in heavily modernised Mi 171sh and it was also translated to English. Probably translation of labels is not top priority for armies
  4. Well, for the Mi24 is it not as common as you might think. I was sitting in the cockpit of Mi35 which is export model of Mi24V. And it was quite young one. Our Czech air force received this one aroud 2005. Whole cockpit was in Russian so i asked the pilot "Do you really need to know Russian language?" And he replies to me " Yes, even flight and maintenance manuals are in Russian". And it will be probably same for Polish air force nad Hungary air force, they even have P models, our Czech army has only V models. For other countries it might be different story
  5. I can confirm this bug. It happened with FW 190 A8 during launch also. I managed to get a screen shot. I was flying level and really there is no chance to fly so fast in the P-47. Multiplayer game on Virtual Aerobatics. Devs please check it :thumbup:
  6. Hi, during my first flight i noticed strange thing. Speed on the tachometr was too big so i changed to F2 view to see indicated speed and it wasn't very close. My altitude was only around 250 meters and dial shows almost 700 km/h but in F2 view you can se 610 km/h. Screenshots attached. I tried an other run in D9 and i didn't notice this behaviour.
  7. Belgian F16 called "Dark Falcon" I really like this one.
  8. I wasn't dissapointed. I was even surprised how long the "stream" was. Why i wasn't dissapointed? Those who watched AJS 37 Viggen TWITCH "reveal" would know why :lol: I really like videos posted by Heatblur - even pre-recorded ones. Keep up the good work Heatblur! :thumbup:
  9. Hi, it seems you are not using Open beta instalation. Yak-52 was released for Open beta only at this time. So switch to open beta or install whole DCS world Open Beta. If this is not the case then contact customer support.
  10. Mobius_cz

    NVG Gain

    I have already made a topic with no response from the devs. I will also be glad for sensitivity setup.
  11. I suppose you are right i have never tried NVG in real life. But this is still a game and the other moduls have the capability to adjust gain and i will welcome this settings even if it is not realistic.
  12. Mobius_cz

    KC 130

    Hey guys, :) i have two questions. 1. Which version of KC130 do we have ingame? 2. Sounds - on my DCS build KC130's engines sounds more like turbofans than turboprops. I just add track. There are C130 and KC130 next to each other. To me, they sound quite different. Maybe it was discussed or it is only in my DCS. build. If not i hope it will be changed :) Thanks C130 vs KC130.trk
  13. Hey guys :), today i tried to mount NVG (changed it for visor) everything worked well but i have little request. I think it will great if we get ability to change the sensitivity of NVG (brightness). Sometimes it can be handy. Cheers :music_whistling:
  14. We will get JA 37 as an AI unit but we will not get full module of interceptor variant.
×
×
  • Create New...