-
Posts
31 -
Joined
-
Last visited
-
Feedback
0%
Content Type
Forums
Store
Third Party - Providers Directory
Feature Plan
Release Notes
Docs
Events
Posts posted by GunnerMBT
-
-
Indeed it is, the project has been put on hold.
-
As fun as it might sound, nobody will go through your entire code and tell you exactly what to do (at least, they shouldn't). Please provide us with a meaningful part of your code, your problem and what isn't working as expected, what have you tried, etc... If you show no research effort whatsoever, why should we?Hey guys, i'm working on a university project and well i missed a few classes i've got the movement working, tank turrent moving etc but i need to get the shooting and collision if the bullet hits the other tank working then automatic reset to starting positions
tank 1 keys
WS <- Movement AD < - Tank Rotation Q - E <- Turret rotation
Tank 2 KeysI - K <- Movement J - L <- Tank Rotation U - O <- Turret Rotation
any help is really appreciatedThe source code is available here: http://pastebin.com/nJzCZgfX
-
The problem isn't the .net framework package, the problem is that the application isn't compiled for 32-bit running systems, and i expect that this problem will be solved.
Target platform is indeed x86, so I'm not sure why that error occurs. Anyhow, I expect it to be solved with the new version which will also include the revamped GUI (bear in mind that I work on this on my free time, so it might and will take a while).
-
Sorry for the delay, use this (put it in appSettings).
- 1
-
The catch is, if you buy directly from OVH, forget about getting decent support. But I don't want to advertise something that is not ready yet
Incloudibly comes to mind for DoS protected dedicated servers, or Worldstream for non protected.
That does not change the fact, that ovh is leader in europe combining protection, hardware and price.
I will test my MG-256 server. I think will only problems with double logging when server is under ddos.
Thing with OVH is that unless you pay for VIP support, you'll get pretty much the less help possible. Don't get me wrong, they'll fix any hardware issues in a blink of an eye, but if you need someone to hold your hand, even in the most problematic scenario, you're screwed. -
My domain was cancelled for no apparent reason, thus the Tool won't be able to check for the latest version and will throw an exception. Nonetheless you might be able to use it anyway, just ignore the exception.
Edit: I've prepared a temporary version which won't check for the latest version, just replace your EterTool.exe with this one.
-
Which operative system are you running? Which .NET framework version have you installed? Have you tried completely unninstalling all .NET frameworks and install only the 4.5 version (it includes backwards compatibility)? Before reporting bugs, please read the FAQ... I am NOT a wizard, guys. -
1.) Visual studio as Administrator
Running Visual Studio as Administrator works. If I run my application there it works too. But building it and running the created executable without VS will cause the error to appear again.
You should skim-read through this. This is your current scenario:
Prepatcher explicitly needs admin privileges, since you're now running in a high integrity level (VS ran as admin) it works fine. It should however prompt you with the UAC message upon hitting the "Debug or Run button", doesn't it?
This is confirmed by my second question:
To fix this, I'd guess you have to edit the manifest file of the target process.Prepatcher as Administrator
Works without any flaws. If I don't run it as Administrator, it'll throw out the error again.
Edit: Also, try what @Sanchez said.
- 1
-
If you run Visual Studio as administrator, and execute the prepatcher within it, does it work? If you run the prepatcher as admin (without VS), does it work? Lastly, if you run the patcher with double-click (normal execution), does it ask for higher level privileges? And you can remove the:
procinfo.Verb = "runas"
Given that you don't want higher level privileges. -
Tiny (not so relevant, but still relevant ) things:
-> You should use the standard naming conventions of C# (procinfo should be procInfo, for example). This is entirely up to you, these are just the usual guidelines.
->
MessageBox.Show(String.Format("Es gab ein Fehler beim Starten des Patchers! /n" + e.ToString(), "Fehler", MessageBoxButton.OK, MessageBoxImage.Error));
Are you sure you didn't mean:MessageBox.Show(String.Format("Es gab ein Fehler beim Starten des Patchers! /n {0}", e.ToString()), "Fehler", MessageBoxButton.OK, MessageBoxImage.Error);
Why would pass all those arguments to String.Format if you have no place-holders? Also, for string concatenation you don't need to use String.Format.-> Might I recommend using another approach on the "logging mechanism"? Regardless of the size of the project, a centralized logging class should be a better approach, one that would enable you to alert the user with custom messages just by changing the message in one place.
The main issue now, if I got it right, you don't want to obligate the user to execute as administrator, then why this:
procinfo.Verb = "runas";
This will prompt the user with the UAC message, asking for higher permissions... -
The average user seems to think the program's UI is a bit too complex given its functionality, and after some thinking, I'm beginning to agree, the main issue seems to be the Main View (https://metin2.download/picture/r3F9504x09DVmF8K988YXgTtGTP6KMUj/.gif). Users tend to discard it completely, and use Quick unpack and Quick repack instead. Given this, I'll be completely re-working the UI before even starting new features (reverse file search, virtual file view, new type support, and the prototype files support, etc), for this, I need your help... I want you to tell me how you'd like the UI to be, the best would be a simple scheme/image describing the structure, bear in mind the following:
- The idea is to make the main view simpler, thus removing the detailed view from it (this would ofc, be available through a context menu)
- Try to think of neat ways to organize all the information (available files to be processed, both packed and unpacked, its properties, etc).
- 4
-
Try with this application.settings file. Also, there still is a bug when packing files (the driver points), I've found where the bug is, I know how to solve it, still don't know the best way though; I'll also be moving to log4net instead of my custom logging class. A new version should be up soon.
- 3
-
No problem. Tell me how you guys think the UI should be improved and which new features you'd like to have.uvv you are awesome really so thanks we waiting for more
thats need really for all
- 1
-
Change-log:
Version 1.1.0.58 - On 25-02-2014
-> Fixed a bug which prevented Quick Unpack from creating valid files.
-> Added 2 new options to applicationSettings (self-explanatory):
- BypassUnpackingIfAlreadyUnpacked
- BypassPackingIfAlreadyPacked
-> You can now select which files to overwrite individually (overriding the global settings)Image
-> Compression level changed to 999 from 1 (it will be slightly slower but the final size will be smaller)
Download from Mega (Or execute ApplicationUpdater.exe)
Also, the Global quick unpacker/packer has been already started, but some problems came up, and it was postponed.
- 1
- 1
-
Is this forum you mentioned the same where your previous post would be considered an insult? It's not his fault you can't control yourself. He could have been more constructive, how does that allow you to insult him? Also, and on topic: this quest prevents nothing nor it protects, it's a nice little "protection" but easily bypassable.Sorry Shogun, but that guy come from "other" forum when rules don't exist trying to put me down.
I don't like that.
I just share the quest for prevent. Not full protection of switch bot.
On my old system i have all structure of python modified, hackshield, that quest, and other small stuff.
-
Type 2 is already supported. 3 and 4, will probably be supported in the future, there are more important features to be developed.
- 1
-
Change-log:
Version 1.1.0.0 - On 24-02-2014
-> Fixed several memory leaks
-> Improved exception handling
-> Minor grammar typos fixed
-> Fixed a bug where Filename CRC hash was not being correctly written (this would cause the client to not be able to read the files packed with the tool)
-> Export to XML implemented (compatible with Tim's unpacker)
-> You can now quickly select/deselect items on the quick unpack/repack window, aswell as set its packing type (repack window)Image
This is the most important upgrade so far, it is imperative that everyone using the tool updates it. Previous versions WILL NOT create valid files.
New version download (Or execute the ApplicationUpdater)
- 1
- 2
-
I can't give you an ETA, since there are more pressing matters (e.g: the leaked binaries source seem to be unable to decompress data compressed with compression level 1, thus files wouldn't work). A new version should be released in the next few days though...what is your status to "export the xml file"
-
Assuming the perfect world in which you'd prevent all ways to manipulate memory, your HWID ban would still be on the client's side, hence completely and utterly useless.
Edit: if you choose to go forward with the idea though, a user-defined ban time according to type of infraction and number of prior warnings would be a neat feature.
-
important things do not work
so not working "export the xml file"
I'm aware of it, I should start working on it tomorrow. Also, I found a huge memory leak which is already corrected. The next version will have both of these implemented and fixed.
- 1
-
Change-log:
Version 1.0.15.0 - On 22-02-2014
-> Repacking now properly updates the progress UI.
-> Fixed a bug where repacking would not get logged.
-> Improved exception handling and minor changes in the Detailed log view.
-> Other small bugfixes.
Regarding the size optimizer, some of you reported that it finds items which are not real duplicates, why does this happen?
Simply because the EIX files are not 100% accurate, the exptected CRC hash is not correct, basically.
Notice how Eter Tool tells you the exptected hash is different (image). But if you compare the output file with Tim's unpacker, it's the same, but different than the exptected by the EIX file (image).
Conclusion: if you want a 100% accurate Size optimizer analysis you must unpack ALL thefiles in your client and repack them again (using my tool or any other which gets the correct CRC hash).
- 5
- 1
- 2
- 1
-
oh my bad
i was wrong put files to folder so thanks for replies
but then when will support type 3 and 4 so just important is thats already
There are some far more important features to implement, it will eventually support them though.
-
-
VT scan addded.My antivirus has detected as a virus
If you will publish the source in the future, why did you pack the exe?
System.NullReferenceException: Nesne başvurusu bir nesnenin örneğine ayarlanmadı.
konum: EterTool.ViewModels.MainViewModel.<UnpackFilesAction>b__20()
konum: System.Threading.Tasks.Task.InnerInvoke()
konum: System.Threading.Tasks.Task.Execute()
--- Özel durumun oluşturulduğu önceki konumdan başlayan yığın izlemesinin sonu ---
konum: System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
konum: System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
konum: System.Runtime.CompilerServices.TaskAwaiter.GetResult()
konum: EterTool.ViewModels.MainViewModel.<UnpackFilesAction>d__23.MoveNext()
--- Özel durumun oluşturulduğu önceki konumdan başlayan yığın izlemesinin sonu ---
konum: System.Runtime.CompilerServices.AsyncMethodBuilderCore.<ThrowAsync>b__4(Object state)
konum: System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
konum: MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)
what i should do
Please read the FAQ. Send me the files, I need to be able to reproduce the issue...
Eter Manager Tool
in Tools & Programs
Posted
Sadly, I don't have a working version anymore, the old project (the public version) was lost during a major disk failure a few months ago. I have a semi-working version which I might tweak a bit so it's at least useable. Feel free to reverse it all you'd like .