Ok, I tried it.

[soaringcow]

Ok, I do have one more bone to pick with my fellow programmers. It is not the user's job to convince you of anything, including their reliability. You, of course, will decide that, but still this is not the user's job. It is your job to take every reported problem seriously and do your best to duplicate them, with the understanding that failure to duplicate is not conclusive of anything.

 

As a last resort, I carefully inspect the probable code in question. It can be surprising what you see. Also, stepping through the code one line at a time in a debugger will turn up things that don't otherwise show. Good luck.

[Guest deleted34304850]

You again have not listened.

 

You need to report the problem FULLY - you have NOT done this. Until you do this, there is NOTHING anyone can do to help you.

Why you fail to grasp this is quite beyond me.

 

Let me ask you this - if you wrote a program and someone used that program and reported that the program you wrote doesn't work, but gives no other tangible information about how/what/why - how do you fix the program?

 

Literally every single post you have made has been missing all the how/what/why. You have claimed a bug, then moved on to something else when shown the solution. You have done this with every post you have made. You couldn't even write down what you had taken from a mod page accurately, Tannin had to go off and piece together a puzzle which looked NOTHING like what you reported.

 

There is no code to debug here,

 

YOU need to step through YOUR process one step at a time - just like in a single-step trace - and come back and tell us when YOU find what YOU did wrong. Until you do that, there isn't a soul on the planet who can help you, because you will not help YOURSELF.

 

I have now reached the conclusion that you are nothing more than an ignorant troll who simply doesn't understand the concept of copying a file from one directory to another and because you don't understand this, you are projecting your own failures, of which there are many, and they are all documented, onto the tool you are (ab)using to try and mod your game.

 

Your own sheer incompetence across so many facets is what's tripping you up here. Not Vortex.

[Tannin42]

Ok, I do have one more bone to pick with my fellow programmers. It is not the user's job to convince you of anything, including their reliability. You, of course, will decide that, but still this is not the user's job. It is your job to take every reported problem seriously and do your best to duplicate them, with the understanding that failure to duplicate is not conclusive of anything.

 

As a last resort, I carefully inspect the probable code in question. It can be surprising what you see. Also, stepping through the code one line at a time in a debugger will turn up things that don't otherwise show. Good luck.

This is like claiming that it's the job of a car repair shop to repair your car even when you didn't bring it in. We tried to tow you by asking you relevant questions

but you refused to answer. At some point everyone no matter how patient will give up and tell you to deal with your own sh*t.

 

And no, we're not fellow anything. If you're a programmer, I'm a Formula 1 driver.

"Also, stepping through the code one line at a time in a debugger will turn up things that don't otherwise show" is something someone would write who once read

the cover of "programming for dummies". Something to put on a nerdy fortune cookie.

 

Vortex isn't a homework project. It's heavily asynchronous for example. The act of stepping through the code impairs the outcome of the program so even if it wouldn't take decades

(literally) to step through all of Vortex (since we still have no clue where to start and where to stop because you haven't described your problem properly) more likely

than not we wouldn't even see anything relevant because every operation would get canceled due to timeouts and even those that succeed would happen in

different order (which shouldn't matter in a bugfree software but since we're debugging because we assume there is a bug we can't rely on that).

Something you would know if you actually had some clue of programming.

 

Debugging in a serious software (anything larger than an afternoon project) only makes sense if you have a very good idea of what you're looking for already.

 

So: no mate. It's not my job to believe everything every user posts. Because if I did, I would spend approximately 5000 hours every day investigating all the reports we get

and not code anything. There is a minimum to the quality of a report before we can look into it. Yours is very far from that.

[rmm200]

I personally regret the amount of time this topic has drained from Tannin's day.

He has better things to focus on.

[AugustaCalidia]

@Tannin42

 

You are a Formula 1 programmer, in my humble opinion.

 

Your Vortex Formula 1 takes the lead in quality and performance. Thank you for this fine piece of mod management machinery.

 

Vortex, the Formula 1 mod manager machine.

 

 

 

[Tannin42]

lol, thank you :D

[Zanderat]

This thread should really be closed.

[HadToRegister]

This thread should really be closed.

 

Considering that the OP just complains, then when asked for details etc, offers up absolutely NO INFORMATION to help solve his "problems", yea, this thread should be closed, because it's actually just trolling

[soaringcow]

>This is like claiming that it's the job of a car repair shop to repair your car even when you didn't bring it in. We tried to tow you by asking you >relevant questions but you refused to answer. At some point everyone no matter how patient will give up and tell you to deal with your own sh*t.

 

If you want professional grade beta testers who document everything and give explicit detail, hire a crew of professionals. They don't work for minimum wage. As for users, we offer what we have without rigor. And we get paid nothing.

 

This is your job, and Vortex is your baby. You want it to be the best you can do, I assume. Users don't have a dog in the race. We are simply trying to use your product for as long as our patience holds out.

 

It is not our job to convince you of anything. But a kindly woncha, whydoncha request for more information without acting like we are the numbskulls we surely are, will probably work better for you.

[HadToRegister]

>This is like claiming that it's the job of a car repair shop to repair your car even when you didn't bring it in. We tried to tow you by asking you >relevant questions but you refused to answer. At some point everyone no matter how patient will give up and tell you to deal with your own sh*t.

 

If you want professional grade beta testers who document everything and give explicit detail, hire a crew of professionals. They don't work for minimum wage. As for users, we offer what we have without rigor. And we get paid nothing.

 

This is your job, and Vortex is your baby. You want it to be the best you can do, I assume. Users don't have a dog in the race. We are simply trying to use your product for as long as our patience holds out.

 

It is not our job to convince you of anything. But a kindly woncha, whydoncha request for more information without acting like we are the numbskulls we surely are, will probably work better for you.

 

You make a complaint, then when someone asks you "What's wrong?" you don't answer.

And instead go on a multi page argument of WHY you shouldn't have to give any details of your problem.

YOU NEED TO DETAIL WHAT YOUR PROBLEM IS.

 

If you were truly a programmer, how would you feel if someone said "Hey, your program doesn't work"

And you asked, "What's not working?"

And the user said, "That's not my job to tell you, that's YOUR job to find out, I don't have a dog in this race"

 

Stop being so purposely vague and obtuse, you make a complaint, then you need to give a detail about your complaint.

 

Would you bring your car to a shop, and when the mechanic asks you what's wrong, or what symptoms you're experiencing like squealing brakes, or loose steering etc, and you answer "That's not my job to tell you"

How unhelpful and useless is that?

At that point you're wasting the mechanic's time, and you are wasting your money, because now you're going to force the mechanic to check EVERY SYSTEM of the car, because you feel you shouldn't have to tell him anything.

 

 

*Mods, please lock this thread, it is just being purposely dragged on by the OP in order to just purposely drag it on.

The OP complains about problems, then refuses to give any info on what the problem is.