Loss of compatibility on v3.2.1.26

[enolgargon]

The plugin is only working up to version r25. With version r25 you can load the plugin and use it without problems, but when upgrading to version r26 Euroscope crashes when opening due to the plugin. If you install version r26 (without the plugin) and open Euroscope, it works correctly. When loading the plugin a problem occurs and the program crashes without showing any error message.

[Kirollos]

Sorry for being late, I will investigate and update you.

[Kirollos]

@enolgargon Can you confirm if the same issue persists on r29?

[enolgargon]

Yes. I found when I upgrade from the r25 to the r29. I thought that it could be a problem with the r29 version because it appears with the text "It might be less stable than the versions before" on the official website. So I downgrade my version until it works. To prevent this testing process from affecting the Euroscope, I did a clean install of the Euroscope on both the r25 and r26 versions. The new installation with r25 worked and the one with r26 did not.

[amosngSP]

Hey, just wanted to follow this issue as well, a fellow controller had the same issue where upon loading the profile, it will crash Euroscope straight away. Just here to follow up on this issue as well, seems like only 1 or 2 controllers had this issue.

[Kirollos]

Hey, just wanted to follow this issue as well, a fellow controller had the same issue where upon loading the profile, it will crash Euroscope straight away. Just here to follow up on this issue as well, seems like only 1 or 2 controllers had this issue.

@amosngSP Hi, which ES version?

[Kirollos]

The weird thing is that I am able to run the plugin fine on both r26 and r29.

[Aracharius]

Can confirm it does not work correctly in r26. Out of the last 15/20ish sessions online, I've only seen DRP populate once.

[Kirollos]

Can confirm it does not work correctly in r26. Out of the last 15/20ish sessions online, I've only seen DRP populate once.

Ok, I will recompile with latest VS and see what happens. I will be giving you a dll to test in few hours today.

[Kirollos]

@enolgargon
@amosngSP
@Hollywood0001
Dear, Can you please try the attached DLL and report to me? Thanks!
DiscordEuroscope.zip

[Aracharius]

@Kirollos Just tried it both as an observer and as ground (made sure both callsigns were in the .txt), discord did not pick up the rich presence.

[Kirollos]

@Kirollos Just tried it both as an observer and as ground (made sure both callsigns were in the .txt), discord did not pick up the rich presence.

But it loads without error, correct? Can you confirm that you receive a DiscordEuroscope message in "Message" window? Also if you are running discord as administrator, you should also run ES as admin.

[Aracharius]

@Kirollos Just tried it both as an observer and as ground (made sure both callsigns were in the .txt), discord did not pick up the rich presence.

But it loads without error, correct? Can you confirm that you receive a DiscordEuroscope message in "Message" window? Also if you are running discord as administrator, you should also run ES as admin.

Yes, I did see the message about it having parsed 5 callsigns. I thought I was running ES as administrator already, but apparently not. Restarted it as administrator, and Rich Presence started working immediately, thank you!

[Kirollos]

@Kirollos Just tried it both as an observer and as ground (made sure both callsigns were in the .txt), discord did not pick up the rich presence.

But it loads without error, correct? Can you confirm that you receive a DiscordEuroscope message in "Message" window? Also if you are running discord as administrator, you should also run ES as admin.

Yes, I did see the message about it having parsed 5 callsigns. I thought I was running ES as administrator already, but apparently not. Restarted it as administrator, and Rich Presence started working immediately, thank you!

Thank you!
I will keep this thread up for a few days if anyone is still having issues, please let me know.

[amosngSP]

Hi @Kirollos sorry for this late reply.

I've sent the plugins to the controllers who are affected by this issue. Waiting to get their feedback on this.