Jump to content

steph1258

Members
  • Posts

    21
  • Joined

  • Last visited

Everything posted by steph1258

  1. OK, so I tried basically everything asked on the troubleshoot guide and I finally elected to uninstall the game to start anew. Unable to donwload the 360+Go from Steam I made the switch to standalone. That did not solve anything either, the error is still here and I cannot play anything now : the game still locks up at World Preload 1/60 (2/60 when I am lucky) so practically unplayable. I have come to the conclusion that DCS 2.9 does not support older configuration now and that new hardware is needed. Unfortunately that in not an option for me, and for quite some time ahead. I therefore have no choice but to quit DCS until better days. It is sad because up until that point everything was running smoothly in 2.8.x even with my old rig. If anyone has any more idea on how to fix that issue, I'll be more than happy to try it out. Until then, have fun on the simulated skies. dcs.log dcs.log-20240101-150546.zip
  2. OK, thanks! I'll see if that sorts out the issue. BTW, I tried shutting down the NVidia and Steam ingame overlays but that did not work either... I disabled them for good anyway to gain some more RAM usage though. If the renaming fails, I really do not understand what is going on since all other games (il-2 for example) work perfectly fine with my rig (albeit with somewhat reduced graphics). And changing the hardware is quite out of the question for the time being...
  3. Ok, so I have a question : I have changed the option.lua file extension to .lua.bak but it did not work. Now do I remove the .bak extension or do I just move on to the next step? BTW, how can that affect my game? Sorry for the stupid question but I fail to see what that extension does exactly.
  4. Hi Flappie, thanks again for the repply. Here are the lines I get: 14:07:21.893 INFO EDCORE (Main): C:\Windows\SYSTEM32\d3d11.dll 2023-12-03 14:07:21.895 INFO EDCORE (Main): # C0000005 ACCESS_VIOLATION at 00007ffaa0cc9c10 00:00000000 Thing is, I also see those just above, and I don't like it: 023-12-03 14:37:45.570 ERROR DX11BACKEND (Main): DX device removed. Reason: 0x887A0006 2023-12-03 14:37:45.573 ERROR DX11BACKEND (Main): failed to create structed buffer. Reason: DXGI_ERROR_DEVICE_REMOVED 2023-12-03 14:37:45.573 ERROR DX11BACKEND (Main): CreateShaderResourceView FAILED. Reason: E_INVALIDARG So far, I have reduced my settings to mostly Low (just Medium for Textures) but cannont understand why it is doing so right now while it morked just fine in 2.8.X... I'll give your troubleshoot guide a try with the xxx.bak instruction, fingers crossed. In the meantime, here are the logs and DXdiag. dcs.log dcs.log-20231203-143746.zip DxDiag.txt
  5. Hi Flappie, thanks for the answer! I did try this but to no avail, unfortunately... The same problem occurs every single time. I really do not know what is happening and I am far from an expert regarding those things but DCS worked just fine in 2.8. It is only since the 2.9 version that I have that strange behaviour. Anyway, thank you for the help, I appreciate a lot!
  6. Hi, seems like this topic is a bit old but I'm having a similar issue with my Steam version since the 2.9 version has landed. My game crashes every single time while I am trying to load a mission, which makes it practically unplayable. I deleted all Mods and associated input files, checked the integrity on Steam twice, reverted to an older version of my GPU pilot : all to no avail. In despair I turn to the community for help because I am at a loss with what to do next... Symptoms : Game crashes when World Preload hits 1/60 then it prompts a game crash report window. I sent numerous reports with a description of what happened every time but since then no answer. Attached are all the files I could find with my latest try, today on 1 Dec. 2023 1740 UTC. Thanks a lot for any piece of advice you can send my way! dcs.log dcs.log-20231201-175402.zip DCS-SimpleRadioStandalone.log DCS-SRS-GameGUI.log DCS-SRS-InGameRadio.log dcs.log.old
  7. Wow! Ok, now you've got my dedicated attention! I'm downloading this mod right now and will certainly spend (more than) a few hours with it while HB do their magic. A huge THANK YOU to all involved in the mod!
  8. So, I've tried a brand new mission and all seems to be indeed fixed. Now for a little analysis: I tried to watch GR's tutorial video to see what could be different from Red Kite's and a sentence kept me thinking. It basically said that after having assigned a formation to the Lead in the Box we were warned not to select the next one right after but rather deselect everything (by clicking the X on the top right corner) and then select the next formation you'd want to modify. If you did otherwise, then it could mess things up. That was something I had not done on my previous missions, I just jumped from one formation to another without closing the window. So this time, I just followed the advice, and IT WORKED! No more wobbling, no more formation breaking, everything working as intended. To be sure, I just tried to make the mission "the old way" i.e. not closing the window and it changed nothing. Therefore, my previous missions must be bugged for an unknown reason but it now works so : GREAT! Now I have noticed that if the Leader of the Box is dead, no bomber would perform the carpet bombing. Is there a way to delegate this task to the next aircraft in the line so that it could be more realistic? Something like "if Lead is dead then task is passed on/carried on by Left wingman" and so on? Or better yet, when the task is assigned to the Box, it is automatically duplicated to each aircraft inside that Box so that every aircraft tries to carry out his task even if separated/lone survivor ? Food for thought but anyway, thanks for the fix and for a great Sim! Hope to be able to give a few good SP missions when I can find some time. Cheers.
  9. Hi, sorry I've been away for a few weeks and could only have a go at it right now. Seems like the problem is still here, sadly... I have run the same mission (see file attached) and the Combat Box still breaks formation upon mission start, perform a 360° turn and wingmen still wobble about their position although not as violently as before. After that, the whole thing seems to unfold pretty well but the Lead formation is well in front and minus 1 B-17 who dived at the very beginning of the mission for no reason. I'll try and make another mission to see if this could be due to the .mis file itself. In any case, I've attached the .mis, .trk, .acmi and log files for you to take a look if you need to. I 'll let you know whether the new mission works or not. dcs.log Tacview-20210104-145553-DCS-Normandy_FW-190A8_Intercept-2.zip.acmi Normandy_FW-190A8_Intercept-2.miz 20210104_WW2 Bombers weird behaviour.trk
  10. Thanks Nineline, we'll let you know when the update releases!
  11. Ok, so I tried the second mission (Normandy_FW-190A8_Intercept-2.miz) without a change and it ended with the same result: -erratic flying and aggressive maneuvering ending up with collision, -first flight keeping its heading (but 3 planes collided due to rapid change of altitude and position) -rest of the box performing a 360 before going back to formation and still behaving weirdly After a quick thinking, could part of this be caused by my changing each plane skill setting within the same box (i.e. having a veteran leading rookies for instance)?
  12. Thanks Nineline, I'll see that hopefully next week and let you know how that turns out!
  13. OK, so I tried to set reaction to threat = no reaction but sadly it did not solve the problem. It even made it worse for some unknown reason. After setting reaction to threat to No Reaction on all 4 flights in the Combat Box, I eagerly tried the modified mission but here's what happened: Individual flights have broken formation upon mission start; They each start a complete 360° before turning on the set heading for the bomb run but without forming up with the rest of the Combat Box; The lead flight keeps its heading while the others perform their 360; All airplane keep on doing their aggressive wobbling around their speed, altitude and position in the flight. There must be something wrong with my setting up the mission or the Combat Box option is just very buggy. Does anyone have in mind another piece of advice or something I might have overlooked in my settings? Thanks in advance! I have included the mission file and the .acmi (in a zip as the forum does not allow for such file extension) and you can find below the link to the video I took on my second attempt at running the mission today. Files : Normandy_FW-190A8_Intercept-2.miz Tacview-20201115-164509-DCS-Normandy_FW-190A8_Intercept-2.zip.zip Normandy_FW-190A8_Intercept-2.miz Tacview-20201115-164509-DCS-Normandy_FW-190A8_Intercept-2.zip.zip
  14. As promised, although a bit late, here are the files (.miz, .trk, .acmi in a zip) plus a little video I made to illustrate the problem. As you can see during the first video rush the leader of the Combat Box is still airborne and the other bombers are acting weirdly. Cheers! Steph WW2 Bombers weird behaviour.trk Tacview-20201106-152113-DCS-Normandy_FW-190A8_Intercept-2.zip.zip Normandy_FW-190A8_Intercept-2.miz WW2 Bombers weird behaviour.trk Tacview-20201106-152113-DCS-Normandy_FW-190A8_Intercept-2.zip.zip
  15. Hi, Not really a helpful answer (sorry...) but I have encountered a similar problem with B-17s box formation on one of my self made mission. My bombers perform weirdly and cannot keep their assigned altitude, position and it often results in collisions with devastating effects... Using RedKite tutorial, I set up a combat box of 4 4-ship elements in close Combat Box (30x30m iirc), with a target assigned for carpet bombing. The aim is to intercept them with 4xFW-190 A8 before that happens. All elements have a different assignment in the group (i.e no-one trying to occupy the same space), they are all created with the same initial altitude of 20kft and speed of 130kt and all have the same bombload of 12 bombs. I just changed the skill on some bombers inside each element so that all gunners don't wipe the FW out on the first pass. ​​​​​​ The problem begins as soon as we sight the bombers, they perform aggressive manoeuvers as described in your post above and they often collide into one another, ruining the whole mission. I tried fixing the problem by making their bomb run into a straight line, thinking my turns were too sharp for them to keep up with (I read >20° was too much). That did not solve anything and even in a straight line they just wobble aggressively around their assigned position (with unrealistic accelerations) and boom! down they go. In my mission, even with the Leader still alive, the group does not behave like a «normal» bomber box and all planes behave weirdly, and at random. I submitted a ticket, thinking this was a bug but the answer was to post in the forum, so I hope that my answer will spark the interest of someone so that we can kill that (those?) gremlins. I'm doing this on my phone so can't post any .miz file for now but will do tomorrow, among with a short video to show the whole thing if I can upload that. Sorry, not the helpful answer you might have expected but hopefully some ED/ME wizard will see this and give a hand! Cheers! Steph
  16. Just downloaded it right now. Thanks a lot to all involved and for all your efforts to make this bird fly! Can't wait to fly her!
×
×
  • Create New...