Ulysses
Ulysses Stuff => General Chat & Help and Support => Topic started by: Storm on March 16, 2015, 11:38:05 AM
-
Since this morning's gmod update to the update, all drop downs in the ulx menu aren't working, I think. So you can't use many functions in the menu such as Command/Event echos, User management, or bans, anything with a drop down menu, because you can't select parameters, I will certainly do an official bug report for this but I just want to be sure it isn't just my servers before I waste anyone's time. I tested this on 5 gmod gamemodes using ULX, seems to be the case on all.
Is anyone else experiencing this?
-
I am not facing this issue. Do you have the latest version from the downloads page?
-
I use NFOservers and they have ULX svn built in. The current version they are using is revision 267, does that sound right? I did a search and I can't find where the most current svn version number is. Also, I am getting no console errors at all.
-
Since we use Git for our version control, GitHub provides an SVN alternative to handle downloads. Needless to say, we can't easily determine which rev is the latest because of that. :P
However, we do try to update the date version of XGUI at the bottom. The date listed should be at least "v15.3.9" for the most recent changes.
I'll try and test the latest gmod version when I get home, as well.
-
Thanks and yes that is the version I have. I see this problem on my servers on the following gamemodes: TTT, prop hunt,Stop it Slender,Hide and Seek, Murder. Slender has the least addons so I deleted every addon and made it a vanilla server with only ulx/ulib on it. The problem seems to still be there.
-
Just curious, have you tried it in sandbox yet?
-
I no longer have a sandbox server. I can switch a server to sandbox but I would have to delete some addons which will cause script errors, or it may corrupt the test. But here is what is odd. I have an addon on a ttt server that doesnt use ulx in anyway but it has a dropdown menu. That dropdown menu also doesnt work only since this update today.
-
Just tested with vanilla sandbox + ULX/ULib on both the dev and main branch of Garry's Mod- no dropdown issues at all. Perhaps you'll want to look into a rouge addon causing this issue? ???
-
I put this on a vanilla server on Slender with no addons but ulx/ulib. hmmm. I don't know if this has anything to do with it but for quite a while, the svn-results log on my server looks like this. I brought this to the attention of my host some time ago, but they didnt think it mattered, Stickly Man, do you have any idea what this means? Sometimes, when the svn updates, it gives other errors concerning sv_groups.
SVN update procedure started Tue Mar 17 09:15:17 2015
-> Handling sync for https://github.com/Nayruden/Ulysses.git/trunk/ulx (https://github.com/Nayruden/Ulysses.git/trunk/ulx) to ulx.
Guessing function of update because folder exists.
PsExec v1.98 - Execute processes remotely
Copyright (C) 2001-2010 Mark Russinovich
Sysinternals - www.sysinternals.com (http://www.sysinternals.com)
The handle is invalid.
At revision 267.
Connecting to local system...
Couldn't install PsExec service:
Connecting to local system...
Starting PsExec service on local system...
Connecting with PsExec service on WIN-R9FA7DOVSI7...
Starting c:\servers\svnbase\svn.exe on WIN-R9FA7DOVSI7...
c:\servers\svnbase\svn.exe exited on WIN-R9FA7DOVSI7 with error code 0.
SUCCESS: Updated svn in 1 second(s)
-> Handling sync for https://github.com/Nayruden/Ulysses.git/trunk/ulib (https://github.com/Nayruden/Ulysses.git/trunk/ulib) to ulib.
Guessing function of update because folder exists.
PsExec v1.98 - Execute processes remotely
Copyright (C) 2001-2010 Mark Russinovich
Sysinternals - www.sysinternals.com (http://www.sysinternals.com)
The handle is invalid.
At revision 267.
Connecting to local system...
Couldn't install PsExec service:
Connecting to local system...
Starting PsExec service on local system...
Connecting with PsExec service on WIN-R9FA7DOVSI7...
Starting c:\servers\svnbase\svn.exe on WIN-R9FA7DOVSI7...
c:\servers\svnbase\svn.exe exited on WIN-R9FA7DOVSI7 with error code 0.
SUCCESS: Updated svn in 2 second(s)
-
Shouldn't matter:
c:\servers\svnbase\svn.exe exited on WIN-R9FA7DOVSI7 with error code 0.
SUCCESS: Updated svn in 1 second(s)
This part means that the svn update command was run successfully.