-
Posts
1280 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by Pizzicato
-
-
@Flappie Great news! Thanks so much for getting this addressed.
-
1
-
-
Good to hear. Thanks Flappie.
-
@Flappie Did you have them check the first stress test that I uploaded (not the on/off test or the one from last year)? It doesn't appear to have any downloads, but I'd be surprised if they were able to get all 50 Hornets started without experiencing the crash.
-
12 minutes ago, Flappie said:
@R-Born So far, devs are unable to reproduce the crash.
Well that's bizarre. Replicating bugs is a weird and unpredictable endeavour.
Thanks for following up anyway, Flappie. I hope someone eventually manages to get to the bottom of this.
-
On 5/15/2025 at 11:03 PM, attackdebris said:
Can you put working Mosquito wipers on our Christmas list please ED.
You should probably be specific about which Christmas...
-
1
-
-
No arguments here. In the meantime, though, you can at least cycle through them with successive mouse clicks (if you didn't already know that).
-
@Flappie In case it's valuable, it seems that the uncontrolled setting isn't a factor.
Because I'm a curious soul, I set up another quick test mission - this time with a single hornet that's already in flight. I then created a simple alternating that toggles EPLRS on and off every 2 seconds. There obviously isn't a real world use case for this, but I just wanted to stress-test EPLRS on a single aircraft without the uncontrolled flag set.
The triggers maintain a count of the ON/OFF iterations in the log.
- Test run 1 crashed silently to the desktop after 59 cycles.
- Test run 2 crashed on the FIRST cycle!
- Test run 3 crashed after 3 cycles (This time while on the "EPLRS to OFF" part of the cycle)
Hope that's helpful.
-
1
-
Thanks Flappie. Much appreciated.
-
PS - Do you have the admin rights to give this thread a more relevant name? It's not really about MOOSE and IDEs now, really.
-
Hey @Flappie
Unfortunately, it appears that the EPLRS bug is very much still alive and kicking unless the engineer you mentioned meant "Never apply EPLRS to an uncontrolled aircraft even if it was STARTED several seconds earlier."
I put together a simple stress test which demonstrates that the crash is reproducible:
- 50 uncontrolled Hornets on the Caucasus map.
- One Hornet receives the Start command
- 3 seconds later, the same Hornet receives the EPLRS command
- This sequence repeats every 6 seconds.
There is onscreen and debug log feedback to mark the progression of the test.
I ran this test three times:
- On the first run it crashed after 4 aircraft had been processed.
- On the second run it crashed after 3 aircraft had been processed.
- On the third run it crashed after 14 aircraft had been processed.
This really needs fixing as it makes setCommand() EPLRS a really nasty and unpredictable scripting-landmine.
-
@Flappie I checked my scripts last night and it turns out that the issue was that I was calling the EPLRS setCommand() immediately after the Start setCommand. I used timer.scheduleFunction() to introduce a 2 second delay and everything started working fine. Thanks for pointing me in the right direction.
On the flip side, I was easily able to replicate the silent-crash-back-to-desktop by calling the EPLRS setCommand on Uncontrolled groups. It's not a major issue given that I now have a workaround, but it still seems that the engine should be able to cope with this issue a little more gracefully (and ideally with some feedback to the scripter).
Regardless, thanks again for the quick reply and helping me figure out what was going on.
-
1
-
-
8 hours ago, Flappie said:
Do you still use `controller:setCommand` function with Uncontrolled aircraft groups?
Hmm... yeah, that's possible. I'm not at my home PC right now, but I'll check my scripts tonight and see if that's what's going on. I'll report back and let you know if that's what was going on.
Thanks for the clarification and the quick response, @Flappie. Much appreciated.
-
On 6/24/2024 at 3:00 PM, Flappie said:
Thank you! Issue reproduced and reported.
@Flappie So... I just spent four hours trying to figure out the cause of DCS silently crashing to desktop during a mission I'm building, and it turns out that it's this exact same issue from nearly a year ago (i.e. too many EPLRS setCommand calls in too short a space of time). Very frustrating waste of an evening.
Can you check the bug database and see if the issue is still there, please? 11 months to address a 100% reproducible Class A crash bug (albeit something of an edge-case) is a little disappointing.
-
50 minutes ago, silverdevil said:
sucks that you @Pizzicato lost your money.
Thanks @silverdevil. I don't really mind about losing the money, though. I was much more annoyed about being sold such a shoddy module in the first place.
-
Each to their own, I guess. It remains the only DCS module that I bitterly regret buying. There's a pretty thorough summary of the associated events here: https://www.reddit.com/r/DCSExposed/comments/1d5r174/the_downfall_of_veao_2019_a_brief_summary_of_the/
Some of the comments perfectly mirror my own experiences with the module. I'd totally forgotten about it shipping with SFM as a full-priced premium module and then charging again for later EFM. I have literally no idea how anyone can have fond memories of that module, but - as I said - each to their own. The only positive from my perspective was that it forced (or at least strongly motivated) ED to significantly raise the bar as regards the third parties they partner with and the quality of the modules they release.
Don't get me wrong - I'd love a Hawk module - just not the VEAO monstrosity. Not ever.
-
1
-
-
The developer (VEAO) had an irreconcilable falling out with ED. They ceased development of the module and declined to hand over the source code so that ED could continue development.
https://www.digitalcombatsimulator.com/en/support/faq/VEAO/
Honestly, no one's missing anything of note. The only good thing about the Hawk was the external model. The rest of it was amateurish in the extreme. It never should have seen the light of day.
-
1
-
1
-
-
21 minutes ago, KevinAu said:
You can’t have a racetrack start at the ‘penultimate’ waypoint. The function needs one more waypoint after that to define the length and direction of the racetrack.
Surely that would be the ultimate waypoint (assuming that it isn't set to "landing"), no?
-
8 hours ago, N2Deepx said:
Was there a solution to this? I'm having a similar issue with the helmet display in the F18 and the George menu in the AH-64
In the two hours between the original post and your reply? Unfortunately not. ED's addressing of bugs and issues (when they even acknowledge them)* is measured in months and years**, not hours.
I'll see you all back here when this gets fixed in 2030 for a celebratory pint.
*A recent bug report about a broken F/A-18 training mission was moved out of the Bugs and Problems forum into the general Missions and Campaigns section.
**Not an exaggeration since I recently got a response to a bug report I'd made in 2022 stating that the bug had now been addressed.
(I do appreciate the issue actually being addressed, though, and the follow up was also very welcome, so it's not all bad.)
-
Oh god! Thank you so much for this. It's been driving me mad (and really hurting my eyes), but I thought it was just me. I really hope this gets addressed, and soon.
-
1
-
-
-
1 minute ago, speed-of-heat said:
It's a feature of active pause... Only your aircraft is paused...
Yeah, I know. I don't really expect this training mission to get fixed for that exact reason. I'm not sure that it can be fixed given that constraint.
That said, it's obviously not ideal that an official training mission is fundamentally broken and unfixable.
-
Hey all,
The second part of the Multi-shot AIM-120 Employment training mission appears to be broken. After loading into the second part of the mission, you start out in Active Pause while being briefed on how to employ your wingman in an engagement. Unfortunately, your wingman isn't actually paused during this period. While you're being briefed, you wingman desperately tries to maintain formation around your static aircraft, getting lower and slower as he circles down into the ocean. By the time the mission briefing has completed, the wingman that you're supposed to directing as part of the training smear is just an oily smear on the surface of the water.
-
28 minutes ago, AndrewDCS2005 said:
Need a compass and range tool (combined) overlay to be able to use on any map. Movable and resizable, ideally multiple instances on one map. Showing true/magnetic bearings taking into account current datetime set on map/mission, relative bearing between any two points. Range built-in, showing distance in currently selected units (metric/imperial).
You really need to explain why something is needed if you want people to understand the issue you're trying to solve and act on your suggestion. What is it that you're trying to do that you can't accomplish with the current implementation of the ruler and compass?
-
I am using 2FA. I haven't initiated any trials, though.
Any ideas why 2FA might be causing an issue? I'm not technical enough to know what problems that might cause.
NVG, HMD, Petrovich "crosshair" All Above Center of VR View
in VR Bugs
Posted
I'm using a Reverb G2.