Jump to content

Ala12Rv-watermanpc

Members
  • Posts

    2427
  • Joined

  • Last visited

  • Days Won

    9

2 Followers

Personal Information

  • Location
    Spain
  • Interests
    Aviation, audio, photography
  • Occupation
    Civil Engineer
  • Website
    https://www.instagram.com/ajmp_photography/

Recent Profile Visitors

41637 profile views
  1. Yeah, I did. "Also, what kind of mods messes with the F-14 and the F-4 shapes file? It seems very suspicious."...dont worry these are mods done by me
  2. Yeah, thats because I forgot to remove the mods before sending the log, sorry... If I remove mods all these errors will go away, but I have the same loading and menus issues even after removing mods and performing a repair, so I dont think there is something wrong with my dcs.
  3. All still the same for me after the patch...utterly slow loading and sluggish menus....actually, I havent seen any line in the patch notes about this problem. Wasnt it supposed to be some fix for this?
  4. Here you have it attached. thanks. Yes, look quite similar. Definitely the bios update made this issue to pop up for sure because a few minutes before performing it, I was running dcs just perfect (thanks to the unpark fix) and inmediately after the update the issue appeared. The problem with this, is that going back to previous bios would be a pain in the a*s, since then secure boot and other problems with log-ins, keys, windows activation, etc. may accour, so Im not willing to do that personally. I think that, even if the bios update has something to do with this, ed should do something about it, since other apps are working fine so hope there is something in the works or in the todays patch that solves this. EDIT:Forgot to mention that also updated intel ME, and other chipset stuff and general drivers after updating bios, at least as far as I know they exist. dcs.log
  5. Hi all! Since I updated my PC to a 13900k back then, I noticed the common issue with menus and DCS in general running slow, crashing, etc. After I used the registry edit to disable core parking EVERYTHING solved inmediately and completely, the game ran perfect as with previous cpus. It has been like that until a few days ago, when I decided to update my mobo bios (Z790 GAMING X AX) from F6 to F13, just to get latest microcode (although I hadn't had any issues with my chip). After that, I inmediately noticed that dcs started to run extremely bad in menus, enter, exit, loading, f10 map, etc , just exactly the same as is used to be before the core parking fix. The thing is, I have already the core parking fix working just fine, so I wonder what is going on or what could be causing this ¿?. The game itself (once in the cockpit), runs perfectly fine and smooth, but just loading the launcher takes ages, then the menus are sluggish, taking a lot of time to load, freezing some time for no reason, exiting the mission or dcs takes ages or crashes, etc. Again, very similar to what happened back then if I let core parking enabled, but now it is disabled so...I tried removing all mods, repairing dcs several times, adding dcs to avira and malwarebytes (already done) with no avail. This started exactly after updating bios, but other than enabling intel limits, rebar, and XMP, I dont remember changing other settings in bios that could be different now. I have game mode on and HAGS enabled in windows, but it was like that previously to the bios update and worked just fine. Any help would be welcome. Thanks!!
  6. Thank you so much for you kind words, really appreciated buddy.
  7. Is this ever going to be fixed?, it is still present in latest build. Thanks!
  8. I would like to up this post again to ask for this feature, at least for the Hornet, since it is a plane that partiularly exhibits these vibrations due to the extreme low speed maneuverability. Here is a recent video showing all this: I think the shaking, buffeting and control surfaces vibrations should be a standard now, at least to the level of the F4 phantom. Thanks!
  9. Yes, there is clearly not enough bending/flex in the Tomcat (and all other modules) since the initial point of the flex is way too far in the outer side of the wing. The flex should start in the infinitesimal start of the wing, inmediately after the insertion with the fuselage, but thats not the case in any module as far as I can tell. Of course, in that infinitesimal slide, the flex is zero (otherwise the wing would be broken) but the point is, the flex starts way too far on the wing, leading to a weak/insuficient deformation in ALL modules. I guess this is done this way to avoid modeling pylons movement but I would love to see improvements in this regard in DCS.
  10. Ok, no problem!, maybe is something harder to solve than I think. Thanks again for the amazing work!
  11. Not a top priority, but this is still present in today's patch. After so long I expected this to be fixed. thanks!
  12. It would be great to be able to activate the selfie mode in the replay, otherwise, it doesnt make much sense to me, sice it is not possible to fly the plane while in the selfie camera. Thanks!
  13. Yep, it worked by creating a new loadout!, thanks a ton!!
  14. It is supposed to be solved, but I can't still arm them. Anyone else?
×
×
  • Create New...