Jump to content
The Dark Mod Forums

hNID

Member
  • Posts

    8
  • Joined

  • Last visited

Reputation

1 Neutral

Recent Profile Visitors

341 profile views
  1. Just to update on the python issue for anybody interested. Especially those using Arch/Manjaro I found out that DR was linking to Python 3 under Manjaro. The program would build but it caused all sorts of bugs including DR to segfault whenever I closed it. It's an old long standing thing because of the way Arch packages Python. In configure and configure.ac there are uses of python-config and some uses of python2-config to get the libraries and build parameters for linking. Well boost.python expects to get the parameters from python-config which on most distros is still symlinked to Python 2 but not in Arch/Manjaro. The program expects python2-config to link Python. You can't use a generalized sed statement to do a carte blanche change either as I found out. The way the scripts call those parameters specifically to get the libraries for linking python and boost.python are intermixed and if you change it with a sed statement It fixes it for one part but breaks it for the other (because Arch symlinks /usr/bin/python-config -> python3-config*). It's very convoluted and my explanation is not a very good one but long story short is on Arch/Manjaro you have to temporary delete /usr/bin/python-config and recreate the link as usr/bin/python-config -> python2.7*. You have to change it back after the build or it will break things but it works as is without monkeying with the code. It's not an elegant solution and I'm going to find a better way moving forward but in case others experience this they have a workaround now. P.S. Still having other issues I'm trying to get around (sound issue with speakers) but I have or will address those in other posts. I'm marking this thread as Solved.
  2. Yes, it's still greys out. I can open the Chooses sound dialog and the file that is currently selected will play. I can start and stop that particular one but if I try to select another sound, Play greys out and won't play any other sound. I can select the other file and hit OK though and then that becomes the current sound at which point I can then reopen the Chooses sound dialog and play the new sound just not while the Chooses sound dialog remains open (without Play greying out again of course if I try selecting something else that is). To answer the second part of your response, yes I can switch sounds but it makes it annoying to pick the right sound you need for your speaker especially if you are new to DR like me and don't know what they all sound like. I'm going to try and set up a capture program and record this behaviour. If I can attach it here then that should be worth a thousand word. It would probably help as well in troubleshooting this. After I do that I'' ll open a bug report. Let's hope it's easy to fix!! Thanks for the reply B.T.W.
  3. Thanks Bikerdude! I 'll keep and eye open on this thread and see if anybody else says anything.
  4. Perhaps what I said above about choosing only one at a time and having to reopen is the proper way this works but it just seems a little weird to me? I thought I read somewhere in the wiki that you could use a speaker as a sound effects chooser inside Dark Radiant without having to use an external sound program? I could be wrong however.
  5. Hi, thanks for the response. It's unfortunately doing it with every sound listed under the shoundshader window that pops up. All the ones I've tried so far end in ogg. I just found out that I can select a different sound even if it's greyed out under the window, press OK then reopen the Choose Sound window and it will play (basically the same as above without having to manually change the shader name first on s_shader) but I still just can't select any sound in the Choose sound window just to hear what that sound is and then pick the one I want. I can select one and then it act like the widow locks up until I reopen it. It's weird and hard to describe.
  6. I have a question about the proper operation of the choose sound window under Entity Inspector -> s_shader -> Choose Sound... I am going through the sections of the A - Z Beginner Full Guide and I just got to the speaker section. In Entity Inspector I select s_shader and Choose Sound. The window pops up and I can select one shader (or the one currently assigned to s_shader) and press the Play button and it will play. If I try to select another sound to see what that sounds like then the play button will grey out and I cannot select anything even if I press Stop or try to go back to the original sound that's assigned to s_shader. Nothing will play at this point and the Play button remains greyed out. I have to press Cancel and reopen the window to listen to the sound that's assigned to s_shader currently. To be able to listen to a different sound I have to manually change the name to the new shader I want to hear on s_shader and then press Choose Sound. I can then Play that one sound but then it greys out again and I have to repeat this process for every sound I want to try. This doesn't seem like the proper way that this should work. Am I doing something wrong? I should just be able to select any sound in the window and play it so I can choose that which I want to use. I'm using the current git version of 2.0.4 pre under Linux. If this sounds like a bug I will open a bugtracker about it but being so new I wanted to ask the community if this is a bug first. Is anybody else having this issue? Thanks
  7. OK, I have had partial success with issues two and three. Apparently Manjaro had a huge update about a week ago as alluded to in the previous post. Well something upstream must have been borked because we had another huge update yesterday and after that I was able to compile again. Also I picked up a newer version of xcb-util-xrm (namely xcb-util-xrm 1.0-2) which seems to have taken care of the crash I was having at startup. I'm still having issues compiling the python plugin without the sed statement but I can live with that. This was really bugging me and I tried everything on my end and it turned out to be a bug in something unrelated. I will try to mark my issue a partially solved in any case.
  8. Hello, Looking for help! This post list three seperate issues trying to compile Dark Radiant from the current git on Manjaro. We are currently using boost 1.60.0-4. First hurdle was there were no recent PKGBUILDS of Dark Radiant in either Manjaro or Arch so I took an old one for 1.8 an updated it for the latest git version. I could not get the Python plugin to compile until I figured out that there are two references to python in configure and configure.ac. One part of the code has python2-config and another says python-config causing (as I later found out) a mismatch between Python 2 & Python 3 which ended in a compile error. I gleaned this from the log file showing flags for both Python 2 & Python 3. I added the following sed statement to the PKGBUILD: sed -i configure configure.ac -e 's/\(python\)2\(-config\)/\1\2/g' and I managed to get it to compile. Note: I think it's linking now to python 3 as I see an error with a print statement in a script when I open Dark Radiant but it compiles now at least. I tried a sed statement changing all to python2 but it failed to compile so I stuck to the above sed statement. Both Manjaro and Arch use python to refer to Python 3 and python2 for Python 2. The second and latest issue concerns Linux makefile update commit abc15b2cad382c4f6655e7eda339d3ed41c7d4dd after this commit I can't compile anymore. It fails with the message Manjaro just updated to gcc-libs-multilib 6.1.1-1 gcc-multilib 6.1.1-1 lib32-gcc-libs 6.1.1-1 and I don't know if that has something to do with it as well. I hadn't compiled since the update. I would like to be able to compile again. The third and least problematic and not really a compile error is when I very first start Dark Radiant I get: This is annoying but when I try again it starts perfectly. It pops up a message saying I should check the log but I don't see any errors. As I said this only occurs the very first time I try to start it up for the day then from there it works fine. Any help or knowledge would greatly be appreciated. I attached my config.log of a recent build if this helps Thanks config.txt
×
×
  • Create New...