Project

General

Profile

Bug #2309

Incompatible addon error appears sometimes

Added by J345 over 5 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Defect
Target version:
-
Start date:
2018-12-16
% Done:

0%

Tags:

Description

Sometimes when I start the game Hexen with Hexen Community Compilation Pack (jXCCP), "missing addon" notice is shown. If I choose running the game anyway, it crashes with segmentation violation error. It happens randomly without any changes in the game or Doomsday config. So if I test the problem and run and quit the game several times, sometimes it starts normally and sometimes it shows missing addon error. I have 2.1 Doomsday build on Windows 10.
BTW, this forum post reports similar problem:
https://talk.dengine.net/discussion/comment/16969#Comment_16969

History

#1 Updated by J345 over 5 years ago

Here is the image of top part of incompatible mods notice.

And here the segmentation violation error notice.
https://ufile.io/xdv4g

#2 Updated by J345 over 5 years ago

To be exact, the name of the bug should probably be changed to incompatible mods error. I cannot edit first post anymore.

#3 Updated by skyjake over 5 years ago

  • Subject changed from missing addon error to Incompatible addon error appears sometimes
  • Category set to Defect
  • Assignee set to skyjake
  • Target version set to 2.3.x

#4 Updated by skyjake over 5 years ago

Have you selected/unselected any of the optional contents in the jXCCP?

#5 Updated by J345 over 5 years ago

I unpacked zip file from Doomsday website, put it in Doomsday folder (it was detected by Doomsday as JHexen Community Compilation pack), added it to Hexen in Doomsday menu and played the game. I left defaults in the mod options setting. At first it worked normally but later incompatible mods error sometimes appeared.

#6 Updated by J345 over 5 years ago

I uninstalled Doomsday and mods completely, made new clean install and the problem seems to be solved. Maybe some forgotten files from previous installations of Doomsday were culprits. If the problem reappears, I will post update here.

#7 Updated by skyjake over 4 years ago

  • Status changed from New to Closed
  • Target version deleted (2.3.x)

Also available in: Atom PDF