XC_Engine [20] - XC_Core [7b] - XC_IpDrv

joker-seqartist.bsky.social · Post by **papercoffee** » Sun Sep 06, 2015 2:24 am

Guys calm down ...no one is trying to piss off anyone...

Post by **Higor** » Sun Sep 06, 2015 5:34 am

I did make XC_Engine not dependant on XC_IpDrv, if LZMADecompress is causing virtual memory errors (switched computer to a somewhat unsupported platform and still no problems) you can solve it easily by removing XC_IpDrv.dll from your System folder.
This way XC_Engine won't replace the default downloader with the lzma one.

Now to play with compilers, gotta see what works best with Windows Server 2012 (I can still install VC++ 6... but I'm curious about newer VS) and if it compiles XC_Engine well.
EDIT: BTW disabling Data Execution Prevention in this OS (all UT apps) fixed most crashes for me.

Post by **RocketJedi** » Sun Sep 06, 2015 3:26 pm

im fine. i think we all just misunderstood each other. No worries

Post by **RocketJedi** » Sun Sep 06, 2015 3:30 pm

sektor2111 wrote:I HAVE READ all posts from this thread, else keep pushing me to clone a bit your server and then don't get frustrated when I'll post ScriptWarnings from server-side and later the cake from client, I see that you insist trying to piss off people but this doesn't work with me .

If I'm posting an error here or other person, suddenly you do try to say NO PROBLEM - happened already. I really don't get what you want to achieve BUT I'm guessing I won't report anything and you can keep blabbering with your PERFECT stuff.
Higor has asked to report any error and this is what I do, nothing more + trying to explain instances. You don't run any of my stuff as long as I did not released anything, and of course you don't know how I'm testing things. If my reports are disturbing you simply take a look into other direction and ignore me, is that simple.

you got it all wrong bro. If you saw what i quoted i said i didn't know about the client version. that's all.. calm down man jeez. no one uses the client version on our server. none of the clients even know that this engine exists. I'm coming from a different point of view. My point was our clients non of which use xc client version have issues. that's it. I think there is just a language barrier here that's making things look different than they are.

Post by **sektor2111** » Thu Sep 10, 2015 10:48 pm

Higor wrote:EDIT: BTW disabling Data Execution Prevention in this OS (all UT apps) fixed most crashes for me.

Yup, I haven't seen issues until this moment, I'll check more this week-end. I gotta admit I don't have too many Giant Levels added but troubles were happening even randomly in a normal load. Only client was suffering.

Post by **Chamberly** » Fri Sep 11, 2015 11:40 pm

Qwerty wrote: no one uses the client version on our server. none of the clients even know that this engine exists. I'm coming from a different point of view. My point was our clients non of which use xc client version have issues. that's it. I think there is just a language barrier here that's making things look different than they are.

There is a few out there that use xc ge as client. That include me so you can't say none used it on your server. ;P Hehe. I basically went to many servers with this thing on just to test out many things and the only problem I get is with 1 mod only so far, AnthChecker.

& if I remember, I advertised or other advertised this XCGE on your forum? Unless it was in a PM. I can't remember. I sent a whole bunch of msgs to other peoples about go give this sweet toy a try.

-------------
Ugh. I made some changes (Upgraded to v15 core2) on Pwnage server and newnet just doesn't want to cooperate. Package loader problem. Flip.

Ps. AdminMovePlayer mod doesn't work with XC_GE. I tried.
Also-BatThwap doesn't work. Using the one I found on medor site, hence I noticed a file mismatch.

Post by **RocketJedi** » Sat Sep 12, 2015 8:31 pm

Chamberly wrote:
Qwerty wrote: no one uses the client version on our server. none of the clients even know that this engine exists. I'm coming from a different point of view. My point was our clients non of which use xc client version have issues. that's it. I think there is just a language barrier here that's making things look different than they are.
There is a few out there that use xc ge as client. That include me so you can't say none used it on your server. ;P Hehe. I basically went to many servers with this thing on just to test out many things and the only problem I get is with 1 mod only so far, AnthChecker.

& if I remember, I advertised or other advertised this XCGE on your forum? Unless it was in a PM. I can't remember. I sent a whole bunch of msgs to other peoples about go give this sweet toy a try.

-------------
Ugh. I made some changes (Upgraded to v15 core2) on Pwnage server and newnet just doesn't want to cooperate. Package loader problem. Flip.
Ps. AdminMovePlayer mod doesn't work with XC_GE. I tried.
Also-BatThwap doesn't work with newnet. Lmao.

none of our regulars use it lol

Post by **Chamberly** » Sun Sep 13, 2015 6:07 am

Qwerty wrote:
Chamberly wrote:
Qwerty wrote: no one uses the client version on our server. none of the clients even know that this engine exists. I'm coming from a different point of view. My point was our clients non of which use xc client version have issues. that's it. I think there is just a language barrier here that's making things look different than they are.
There is a few out there that use xc ge as client. That include me so you can't say none used it on your server. ;P Hehe. I basically went to many servers with this thing on just to test out many things and the only problem I get is with 1 mod only so far, AnthChecker.

& if I remember, I advertised or other advertised this XCGE on your forum? Unless it was in a PM. I can't remember. I sent a whole bunch of msgs to other peoples about go give this sweet toy a try.

-------------
Ugh. I made some changes (Upgraded to v15 core2) on Pwnage server and newnet just doesn't want to cooperate. Package loader problem. Flip.
Ps. AdminMovePlayer mod doesn't work with XC_GE. I tried.
Also-BatThwap doesn't work with newnet. Lmao.
none of our regulars use it lol

Shame, you should let them use the benefits of less crashes and stuff.

Post by **Higor** » Thu Sep 17, 2015 8:52 am

Since I'm feeling like whacking my head against my screen a few times, I'll port the whole codebase to Visual Studio 2015
:redeemer1:

Let's see what new dangers await on this new road.

SC]-[WARTZ_{HoF} · Post by **SC]-[WARTZ_{HoF}** » Thu Sep 17, 2015 3:28 pm

I'm looking forward to testing the next release. Hope VS 2015 works for your project.

Post by **Higor** » Thu Sep 17, 2015 5:36 pm

I was contemplating working on the main platform's output device, in english: the log.
Problem here is... the log window is entirely controlled by the launcher, and it does some really nasty shit.

So if we want enhancements on the log, we gotta make a new launcher instead!!
@Chamberly, got the custom UT launcher's source?

===
First, I'll port this to Visual Studio 2015 which uses the latest c++ standards, and therefore spams the entire compilation with thousands of warning of all kinds (because UT codebase is extremely hacky).
I'm slowly editing headers and pragma-ing the least significant warnings out, but some other stuff is more intrincate and will take some time to port, I might as well look at UE4 again, since UE4 is supposed to build with VS2015 just fine (i guess).

What's worse is... I have to make my code c++ 11 compliant for VS, and old c++ compliant for GCC 2.95.
So my question...
DID IT REALLY KILL GCC DEVELOPERS TO ALLOW GCC 4.XX.XX BINARIES TO BE BUILT USING THE 2.95 NAME CONVENTIONS????

Sure, Linux developers love going by standards and setting everything on their own way of 'right', but sometimes it involves putting a huge stick up the ass to whoever wants to make stuff backwards compatible.

Post by **sektor2111** » Thu Sep 17, 2015 9:27 pm

My thoughts:
- New stuff if involves bunches of normal client tweaks will lead nowhere;
- All GB×100 stuff if won't run "properly" as runs now then... all UT'99 fans are not going to be happy;
- However, stuff for debugging a la XC_Core's clocking system might be useful for coders to gain the best code optimisation but not dependant on new stuff in final releases;
- If new stuff will be unstable probably people will going to lose patience with fixing/dealing with a complex setup.

Aside: Very ugly shite happens at this moment randomly in client using v15 (even tweaking that "data execution"). At a moment display went garbled. Through some stupid colored lines I clicked again on UT icon (presumed location since it was badly ruined), game has been loaded and then after exiting it, everything returned to normal state in display. Looks like parts of video memory have been messed somehow. I did not see ever such things in versions until and including XCGE13. Something probably went rammed from compilation related to those "threads" or who knows, I don't know that, else I would be the first in helping with these C++ things.

Edit: I went to solve everything which was supposed to be solved even in custom CTF DM (optimisations only since I don't have many errors in server - that client + weaponry, eh...). But... 2 times I have been dropped without to know why - nothing was logged bad in client, it was like I did a manual disconnect. When I was using default stock stuff with a mountain of errors at least I could see server-crash reasons (PlayerCanSeeMe(), Collisions bullshit, Netdropped for some stupid necode, Screwing Object array, some "cute bytes" coming from network, etc). Now I'm frustrated because these errors are history but new troubles seems INVISIBLE, I simply cannot see why is CRASHING (client)

. Or do I need to scan logs from OS ? That's new to me.

To not forget, please do not make Engine compatible/dependant with any NetFrameWork - is was proven a crap still NOT READY + manure only a la M$.

Post by **Chamberly** » Thu Sep 17, 2015 9:40 pm

http://coding.hanfling.de/launch/
Should be on the webpage somewhere.

Post by **Higor** » Fri Sep 18, 2015 1:25 am

Be at ease, I'll make sure the build is purely c++
If it makes you feel better, VS 2015 crashes a lot more than UT + xcge

=================
EDIT:
Adding 'FORCEINLINE' to most of TArray<T> methods allowed me to use TArray<BYTE> without linker errors.
This makes sense because we're still calling FArray:: methods, so force inlining doess more good than harm, and UE3 does it!
@anth

=================
Ok, UT launches and all here, anyone brave enough to make a backup and try it?
It is a v15 dll, and it's surprisingly smaller.

XC_Engine.zip: Test DLL
Built using Visual Studio 2015 - Windows Server 2012; (74.43 KiB) Downloaded 69 times

Post by **Chamberly** » Fri Sep 18, 2015 5:34 am

Gonna test it now.

edit:

Spoiler

For old stuff. :L
Client side.
Warning: SpawnActor failed because class Boulder2 has bStatic or bNoDelete
Warning: Actor not spawned for new channel
yeahhhh-LOL...

ScriptWarning: XC_AdvancerTicker CTF-SpaceWars(R).XC_AdvancerTicker2 (Function LCWeapons_0015.XC_AdvancerTicker.Tick:005A) Accessed None
everywhere. -.- Nothing to do with this XC GE Build.

Warning: Failed to load 'dusk': Can't find file for package 'dusk'
I didn't see this coming. That slipped away without me noticing unless I was very quick to get away from that msg on the screen?

XC_Engine [20] - XC_Core [7b] - XC_IpDrv

Re: XC_Engine [15] - XC_Core [2]

Re: XC_Engine [15] - XC_Core [2]

Re: XC_Engine [15] - XC_Core [2]

Re: XC_Engine [15] - XC_Core [2]

Re: XC_Engine [15] - XC_Core [2]

Re: XC_Engine [15] - XC_Core [2]

Re: XC_Engine [15] - XC_Core [2]

Re: XC_Engine [15] - XC_Core [2]

Re: XC_Engine [15] - XC_Core [2]

Re: XC_Engine [15] - XC_Core [2]

Re: XC_Engine [15] - XC_Core [2]

Re: XC_Engine [15] - XC_Core [2]

Re: XC_Engine [15] - XC_Core [2]

Re: XC_Engine [15] - XC_Core [2]

Re: XC_Engine [15] - XC_Core [2]