All Activity

Thanks @Schmidtfire I will try your method out, I was wondering how to make it work!

This may be resolved in DCS 2.9.20.15384; at least in one play through Zeus reports taking ground fire but no "getting hammered" message or mission failure.

@Calvin.Pimax The tech got back to me with the following " The DCS process exit codes were 3221225477 and 3221226505. In Windows, these codes indicate a memory exception, which suggests that DCS may have encountered a memory-related issue. Could this be due to in-game settings being too high? I recommend reaching out to the game developers and providing them with these exit codes for further assistance I did post this in the "game crash" section of the forums. Do you know who generally would handle a question like this? I dont notice any memory type issues with normal use and I didnt have any crashing issues before with the G2 or the VR1. I dont think the settings are too high Im still getting a very reliable 90fps out of this now since the last update... That has remained constant and there are now 0 performance issues like I had in the past. It run excellent until it crashes. Thanks

I tried deleting that file and repairing but it didn't work did you alter your default view by any chance?

@silverdevil I submitted a ticket to Pimax and their system includes automatically uploading a bunch of logs. I got this reply from the tech. "The DCS process exit codes were 3221225477 and 3221226505. In Windows, these codes indicate a memory exception, which suggests that DCS may have encountered a memory-related issue. Could this be due to in-game settings being too high? I recommend reaching out to the game developers and providing them with these exit codes for further assistance" I have 64gb of ddr5. There is no noted system instability outside of dcs and pimax or pimax and halflife alyx which appeared to crash as well. There was no crashing issues with the G2 beyond the normal DCS issues which were very rare. The pimax tech suggested that perhaps a DCS person would know what to do with the "exit" codes I have no idea who might find that useful if anyone at all. It appears to be of little value but if you know or know anyone who might be able to further isolate an issue let me know I can direct that to them. Thanks

They probably never do it for FC modules, but when the FF Su-25 drops, I expect to see it, even if I've never used it.

Unforunately I'm away from home for a couple of weeks and I've forgotten the specifics. It's been a while since I did it. Check out the pdf in the first post there. I seem to remember something about the "pressed" function doing it. See chapter 5.8 in the pdf.

Since it was the easiest to make without properly modelling it, that's what it feels like at this current moment, and how most of this topic is being ignored. There are so many documents and SMEs that proves the complete opposite that what is implamented. I would rather have the "chaotic" readings in HPRF, and properply working RWR in MPRF Insted of being blasted by an aircraft that we don't even know that is locking. Currently a MiG-21 has more SA than a way more advnaced MiG-29. But hey, more importantly that all other jets have magic rwr that detects things that it shouldn't even, but the SPO can't even work with it's radar on (that was designed to operate it)

Thanks @Devil 505! Awesome pictures @ViolentNomad!

I'm running through this exact issue when I host a mission. We tried downloading this test mission with the same results when I host. Oddly enough, when my friend hosts it, I'm able to see the names of the JTACs which leads me to believe that it's something on my side. I decided to rip out DCS and reinstall since I hadn't done so since the stable and openbeta versions merged. Any idea if there's something on my end that may be breaking this? We've tried several missions, including the attached simple mission we created that has the same behavior as the test: when I host, my friend can't see JTAC names, but when he hosts, I can. Any insight you guys have would be incredibly helpful. testjtac.miz

I've released v1.5.0. Highlights include: MiG-29 Full Fidelity support, SRS recording support, and some minor improvements to speech recognition quality. https://github.com/dharmab/skyeye/releases/tag/v1.5.0 On a personal note, development is slower now because of other stuff in my life being quite busy (my professional work, home improvement projects, non-digital hobbies, and family time). I hope to resume major development in the future but for now expect mostly maintenance rather than big new features. Yes, when you run local speech recognition on Windows or Linux, all available CPU cores are used, and newer, faster CPUs perform better. See the hardware section of the admin guide: https://github.com/dharmab/skyeye/blob/main/docs/ADMIN.md#hardware Some people have made forks of SkyEye that can use GPU acceleration on Windows and Linux, using CUDA or Vulkan. I'm interested in adding support for this in the standard build, but have two obstacles: 1. I don't have any nvidia GPUs to test CUDA 2. Limitations on my time mentioned above I would strongly consider using the OpenAI API, if possible; it's _really_ cheap and works great. Running on local CPU should be considered a last option if a Mac or the OpenAI API is not possible. No, SkyEye bypasses all SRS effects. SRS radio effects are client-side; you can customize them or turn them off in the official client. SkyEye uses custom code instead of an official SRS client, and simply does not implement any audio effects, instead directly converting the SRS network packets' data into the format used by the AI models.

He was writing one can start the engines without a running APU and without ground power. How does that work?

Here is a video from last week. Getting back into it and hoping the boys can join soon. We also, I just posted some photos from ViolentNomads discord of the AH-1G Cobra. Looks like it is getting close to release. Link below to the forum I posted it in if you do not follow him on discord. We will add this to Into the Jungle on its release. Also did some touch up to Antonio Airport a bit.

Anyone looking for an update on ViolentNomads Cobra, I just posted a bunch of updated photos from his discord. Sounds like he is getting close to release.

Anyone wanting to keep up more frequently, I would say track his discord. Apparently she is getting really close to release. To help VN out, I grabbed some of his latest screens from discord to put on this thread for him. @ViolentNomad Just FYI. null

"Since the automatic ATP went online, I haven't used the AGM-65D. I played with it for a while yesterday, and I'm quite certain that the AGM-65D's image is much blurrier than before. The image processing seems somewhat like a weakened version of the ATP. I haven't tested it with the LITENING pod combined with the AGM-65D yet, but I suspect that the blurriness of the AGM-65D's image is due to the combination of ATP and AGM-65D."

I will immediately purchase the NS430 if the Su-25 can integrate it.

Anti Virus or in my case Windows Defender

That did the trick.

Yes I did! Did you do the same for mine?

Yes, I will focus on fixing wmd7 bugs till the end of 2025 (probably overhaul since SDK is always updating with new features). Sorry that we are a small team and part time for DCS JF-17, I will try my best to enhance player's game experience during my free time.

what is AV in this context?

Something about the Kiowa FM has bugged me since it came out. When hovering with a moderate tailwind, or hovering backwards, the aircraft does.... something I don't understand. The rotor RPM spikes off the chart, the aircraft starts falling as if it's in VRS (but it's not), and yaw becomes nearly uncontrollable. I feel like this might be trying to simulate LTE, or VRS. But it can't be VRS because it occurs with no descent rate, and it can't be LTE because the pedals are still effective. Neither explains the spike in rotor RPM. I've attached a track. What the heck is this??? In 2000+hrs flying real helicopters I've never seen or heard of anything like this. Please tell me it's a bug and it will be fixed, it's extremely annoying - combat does not always allow one to hover into wind (the enemy could be downwind from you!) kiowa tailwind.trk

It would have been so much cooler if they had named him "Bob" instead of "George".