Jump to content
The Dark Mod Forums

Yodle

Member
  • Posts

    5
  • Joined

  • Last visited

Reputation

0 Neutral

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I'd be happy to do some testing! I hope to actually dig into your code at some point (I think it's totally awesome that you guys are open source!) but I can't make it happen this week. I have some experience with C and C++ but I'm not familiar with scons yet. As for the gcc flags... I've struggled with that in the past and I'll have to take a look. They're sometimes counterintuitive.
  2. You don't have this problem with the Windows binary (I know this because I can start dark mod on Windows on my XP 3200+ system without crashing) so you're either not using SSE2 instructions on Windows or you are using a separate code path for the different instruction sets.
  3. I am confused. I'm running dark mod as a mod to doom 3. Is there another way to run it?
  4. I hear you. I wanted to actually look at the code and provide a fix before commenting, but I'm pretty busy and I'm not sure when I will have time. If you guys really don't have anybody working on Linux right now maybe I should make that a priority. What platforms are the current devs working on? I really think i30817 is right and it's a matter of disabling those instructions at build time. While he's got a good idea, I'd go further than he did and say that you can just disable sse2 arbitrarily, rather than making a separate 64-bit executable. I pretty strongly suspect that having sse2 instructions in there won't make much difference in terms of performance. (in the renderer or something else in doom3 would be a different story, but that's not a concern until you're integrated with the doom3 codebase)
  5. For what it's worth, this error still exists. Installing the software onto an Ubuntu 12.04 system with an Athlon XP 3200+ (32-bit Barton) works fine, but execution of the program halts as WWWWolf described. I am pretty sure WWWWolf's analysis is correct and the binary's trying to use SSE2 instructions when it shouldn't (on a CPU that doesn't have them). The Dark Mod runs fine on the exact same hardware running on Windows XP. Doom3 itself runs fine on both Linux and XP on this machine. I hope that helps.
×
×
  • Create New...