Jump to content

markbond

Members
  • Posts

    41
  • Joined

  • Last visited

Everything posted by markbond

  1. Another CTD. I have had this with the latest reinstalled nvidia game ready drivers and the latest studio drivers. Also had it with Nvidia debug mode enabled. Windows event viewer: Faulting application name: DCS.exe, version: 2.7.11.21408, time stamp: 0x62331190 Faulting module name: edterrainGraphics41.dll, version: 2.7.11.21408, time stamp: 0x6230e527 Exception code: 0xc0000005 Fault offset: 0x00000000000cb68d Faulting process ID: 0x2128 Faulting application start time: 0x01d83bc603447ab7 Faulting application path: C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\DCS.exe Faulting module path: C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\edterrainGraphics41.dll Report ID: d27b75aa-7e7c-4962-87bf-f61740f81129 Faulting package full name: Faulting package-relative application ID: dcs.log dcs.log-20220319-205601.zip
  2. I get repeated random CTD with the AH64D in Win11. Generally occurs after 5 mins of flight with no specific triggers. Win11, i5 9600K, RTX38030, 32Gb page file, Nvidia studio drivers 511.65 (also with game ready drivers). Log attached. Last entry 2022-03-19 11:40:52.529 INFO APP: try to write track file dcs.log dcs.20220319-114052.crash dcs.20220319-114052.dmp dcs.log
  3. Can anyone post a link to the patch or update to Moose that is supposed to fix this? All I can find is 2.4.13 that corrects a documentation issue. https://github.com/FlightControl-Master/MOOSE/releases
  4. Apparently this crash with InitRepeatOnEngineShutdown was fixed by funkyfranky https://github.com/FlightControl-Master/MOOSE/issues/1076 in the development branch of Moose. Is this a different Moose/lua file? Where would I get this from? Thanks
  5. Does anyone know if the new Jan2019 update fixes the crash caused by InitRepeatOnEngineSHutDown()? Thanks
  6. This works local flight1=SPAWN:New("FLIGHT1"):InitLimit( 2, 10):SpawnScheduled(30,0) flight1:InitRepeatOnLanding() flight1:Spawn() but for some reason this spawns three units not 2.
  7. Any idea why when I include the limit function nothing spawn? Without it FLIGHT1 repeatedly spawns every 30 seconds, as expected. I want just two to spawn and if one dies another spawns to take its place. flight1 = SPAWN:New(FLIGHT1):Limit(2,10):SpawnScheduled(30,0) flight1:spawn()
  8. Can anyone explain to me the route randomisation? Is the first number the number of the first waypoint randomised, the second number the waypoint where randomisation ends, and the third the radius of randomisation? If so ehst foes (1, 1, 1000) do? I see similar to this with equal firdt two numbers. Confused!
  9. I have A10C and Ka50. A10C performance is much better than 1.5. Ka50 is much worse. On 1.5 both performed well. But in 2.5 A10 is good (60 fps on high) and Ka50 bsd (30 fps same settings)
  10. I have passed the BFT01 ground handling mission twice now. The second time I even saved the log file. I wait for several minutes after the instructor say I passed, then I quit and save the log. However, when I got back into the campaign it only lets me re run the BFT01 ground handling mission and not progress onto BFT02. Am I doing something wrong? Thanks
  11. Hi Thanks for the advice. yes I read the manual and watched the training tracks. Just had a bit of trouble implementing it. Must have missed something. Just to confirm, when the bug is fixed, I should be able to laser a point and get my wingmen to go there, but how to I send then point via the datalink? I guess I laz the point, click 2 on the PRT (?), then save/send then give the order to move to datalink point? Is there a target point button I would also need to click as when creating an ingress point? Thanks again. Mark
  12. here is the track of me making an ingress point, sending it to a wingman and then ordering him there, followed by a NEGATIVE!!! Any pointers? Thanks datalink ingress.trk
  13. Hi All, have recently been trying to learn the datalink system. I can now designate targets and get the wingmen to engage the datalink targets. I can also create ingress points that appear on the ABRIS. However, I cannot get the wingmen to go there. I designate the ingress point with ths schval thingy, press the ingress button on the PRT (? top right) and then save/send. This makes it appear on the map screen. I then select that ingress point with the ingress point button, press 2 (for wingmen 2) and send. I the order the wingman to go to the data link point but he always replies that he cannot or is unable. Any ideas as to what I am doing wrong? Maybe I should upload a track? Thanks Mark
  14. I see that there are controls to slew around a landing/search light but I cannot find the button key combo to turn on the light. I can control all the nav lights etc but I am sure I have seen a track with a light that illuminates the land/runway in front on the heli. How do I turn this on. I have tried RCTRL+L but that does not appear to work. Also cannot find a switch in the cockpit. Am I imagining it or does this light not exist? Thanks Mark
  15. Just downloaded DCS max to allow me to change skins. Was just wondering if there was an easy was to browse the skins to see what they look like before selecting them? Are the seperate graphics saved in a folder somewhere? Thanks
  16. mapped the joystick hat button to the optical slew and no problems now.
  17. I just had a look at the track myself and you are right. The sim is reporting left cyclic input. However, I did not input is myself via the stick. I took control of the track and pressed /? again. When holding this button for more than about 2-3 seconds I get a clear left cyclic input. The virtual stick clearly moved to the left even though I did not have my hands on the stick. Why could this be? Thanks Mark
  18. I didn't look at the cockpit cyclic stick myself but I definately did not enter left cyclic via my joystick. I do not think I was even touching the stick at the time. Could it be that the ?/ key, when held down is interpreted as a lefy cyclic input? Will try it again but I am pretty sure I am not entering left cyclic via my joystick. Thanks for looking at the track. Mark
  19. I haev noticed recently that if I hold down the /?, key to slew the optical tracker to the right after a few seconds it appears to make the chopper drift to the left. I then have to re trim it back to center. This does not happen with the right, up or down slews. I also do not have the move to target button pressed. This is very annoying as it messes things up as I am lining up on a target. Any ideas? I have attached a track file optical tracker problem.trk Thanks
  20. I cannot find the short cut key to activate the night vision goggles. From the manual it appears switches relating the NVH are on a panel behind the cyclic stick and so I cannot properly see them. Is there a way to remove the rendering of the control stick to access the panel behind or is there an easy short cut? Thanks
  21. Was playing one of the campaign missions last night, the second mission I think where I had to attack a rebel camp. Anyway, was climbing up a mountain at about 2000m and gradually lost the ability to gain altitude even with max collective. Kept getting the Max RH and LH something lights lighting up on the overhead panel. When I encountered this problem I turned on the anti iceing of the rotors and engine but that did not help. Maybe too late? Is there any cause of my lack of ability to gain height and get over the moutain ridge? Thanks Mark
  22. thanks for looking at the track file. I was sure I checked and un checked that setting in the mission editor as well?? Anyway, this evening I disabled force feedback in the mission editor and It appears to work now, at least in the campaingn files. Thanks.
  23. still getting the same thing, even though I now hear the clicking noise of the trim. I see from another post that someone suggested that force feedback can interfere with the trim. I cannot see how it can work in training and not in the missions though. I wonder if disabling FF will help?
×
×
  • Create New...