Jump to content

red_FoX

Members
  • Posts

    24
  • Joined

  • Last visited

About red_FoX

  • Birthday 01/16/1972

Personal Information

  • Flight Simulators
    DSC, MSFS 2020, Elite Dangerous
  • Location
    Serbia, Senta

Recent Profile Visitors

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

  1. I was thinking that if the shader recompilation process needs to take some time, it should be useful to show some kind of message about that, so we should know that some regular process is underway and the game is not frozen because of a bug.
  2. After I enabled the full debug log with your autoexec.cfg, I saw this line: 2022-09-17 17:30:02.211 ALERT DX11BACKEND: Error: Can't find precompiled shader for effect deferred/compose.fx:DIRECTX11=true;MSAA=2;USE_DCS_DEFERRED=1;USE_SHADOWS=1;USE_SSAO=1;. Recompilation process will take some time, please wait (this situation should not occur on end user PC, if there is no manual shader editing) This time I gave the game 10 minutes to load, and it finally loaded. Now it is loading normally
  3. Today I updated the game to 2.7.17.29493 open beta, and after I try to start the game, it fails to load. After the user login, nothing is happening. On the taskbar, I see the DCS program with the info "Loading...". Sometimes it goes to the black screen with a wait cursor and after a while, Windows displays a message that the program is not responding. I have attached the dcs.log and DxDiag files. What I have tried so far: Removed all mods (Tacview was the only mod I'm using) I have deleted fxo and metashaders2 folders Renamed Config folder Disconnected all the hardware I could (e.g. joystick, track ir...) Any ideas? dcs.log DxDiag.txt
  4. I can confirm, that after the last update (DCS 2.7.1.7139 Open Beta), the situation with this issue is much better. I made a small video that shows how it looks now, with the same graphics settings as I posted before (MSAA 4x; SSAA Off). Pay attention to the bottom of the aircraft, when the white cloud is behind!
  5. In addition to the problem I have described in the post https://forums.eagle.ru/topic/268916-aircraft-edges-problem-when-the-aircraft-is-in-front-of-the-clouds/ I found another problem related to antialiasing settings. When I change MSAA or SSAA settings, after the mission load, the game crashes to the desktop. I have sent a bunch of error reports after the crashes. Sometimes, the game doesn’t crash, but the graphics became broken. After the mission load, the game looks like this: or this and this instead of this After the restart, graphics become normal, but after the next change of the MSAA or SSAA setting, the problem reappears! I didn't have this problem before 2.7. I have tried to delete a "Saved Games\DCS" folder, but that doesn't solve the problem. The repair option was not helpful either. My system specs are: AMD Ryzen 3 1300X 16 GB of RAM Asus NVIDIA GeForce RTX 2060 graphics card, with latest drivers Kingston SSD Windows 10 64-bit with latest updates installed.
  6. Does anyone have a problem with aircraft edges when the aircraft is in front of the clouds? Please see the provided screenshots. "Effect" is present on all types of aircraft I have tested (all FC3, F-18, MiG-21...) and it only disappears, when I set SSAA to x2, but then the FPS drops down drastically (from 60+ down to ~20 FPS)! I have provided the screenshot of my graphics settings too. I'm using NVIDIA RTX 2060 graphics card, and before 2.7 I haven't got this "effect" on aircraft edges.
  7. That was a problem! Thank you! I didn't wait for full INS alignment. Alignment took me ~8 mins to complete, but with "STD HDG" option enabled on the HSI MFD, time for the alignment is drastically reduced to ~1,5 mins! And a little update for my first post. Only BALT and RALT autopilot options had a problem if I take off without INS aligned.
  8. After I do a cold startup (as it is described in the tutorilal), autopilots are not working. When I press A/P button I get labels ATTH, HSEL, BALT and RALT, but when I click on the appropriate button, nothing happens and I don't get the "colon" indicator that the autopilot is active. When I do an automatic startup with LWin+Home, autopilots are working properly. It must be that I'm missing something during the startup! What? I'm using newest Open Beta v2.5.6.59398.
  9. Bug confirmed on non-Steam version too (MiG-29, F-15...). But, no matter what I have tried, I couldn't produce blackout state on SU-27 at all!?
  10. Light is not at old place (at front panel). I suppose you are looking for it there ? Look at panel near pilots right leg (a bit back). It is there in SU-27/33.
  11. I have reported this issue in FC3 bugs thread after a previous patch, but seems it is not solved. It is not a big problem and does not affect gameplay, but I'm sure its not hard to correct this issue too.
  12. Thank you for your answer ! I have found MIST instructions on this forum, so I'll try to make a mission as you described.
  13. After patch 1.2.4 problem still persists. Any chance to fix it in some of the next patches ?
  14. Probability of presence in mission editor is great option to avoid lineariti in missions, but I'm wondering if it would be possible to add something like "radius of deployment" ? This would make missions more interesting and dynamic, because enemies could spawn then on different positions on each mission start.
×
×
  • Create New...