- Joined
- Nov 14, 2008
- Messages
- 1,025
- Reaction score
- 641
Yeah I'm already considering not going down the nexon route again just because of that
also, a cool fact: if you ever opened 2 clients together to test, you'd notice that when you move, that character moves about a sec later in the other client. this is indeed because of the delay to calculate the interpolated movement
Why use suckson's packets... Change up the entire packet structure altogether, and change this to match it....
He already used his own packet structure however he wants this client to be compatible with real servers.
Yeah, just for us to test it for now. I think he plans to use his own login
so ??? customer support is worse than nexon
I think he should go with Neckson's format for now and make it work for actual servers and then, once the client is considered playable, edit it to make it work with his server's format.
If you have an actual problem send me a pn and provide more information. From the ss you posted I can't even tell if that's my program and if you're running windows (or even if you're just trolling).
Yes this is probably the best solution.
bro this is windows 10 and I ran it and it shows a white screen, just like the picture shows
On the very same page of your original post, I said that I don't know if it'll work on windows 8 or 10. I can't help you with that, I don't even have windows 10.
well dude you need to make it work, a large part of the market is windows 8+, you're wasting your time if your product does not even work inside the main OS'
I disagree. Windows 10 (which sucks) is behind 7, XP and 8.1 according to this:you're wasting your time if your product does not even work inside the main OS'
Lol.. you are essentially trying to force SYJourney to implement this to other OS when the actual product is still under development in the current OS he has. You will just have to wait for him to finish everything in the current OS he is on, then I would assume add other OS and test them there.well dude you need to make it work, a large part of the market is windows 8+, you're wasting your time if your product does not even work inside the main OS'
1. Windows 10 is behind 7, 8.1 and XP according to this:
Not unexpected cause it 8.1-10 looks like a cheap cross between vista and a windows phone with a lot of poop broken.
Lol.. you are essentially trying to force @SYJourney to implement this to other OS when the actual product is still under development in the current OS he has. You will just have to wait for him to finish everything in the current OS he is on, then I would assume add other OS and test them there.
Understand he is testing and working on his OS specifically. He will not change/add support to others because someone might qq "this error xxxxxx is happening in Windows 8/10/98/etc halp.". It will slow down his development and frustrate him because he will need to stop his current work and fix the OS error through trail and error(assuming he doesn't have another OS machine).
It's often a good idea to know what your target platforms are in advance so you can choose which APIs to use. Who knows, maybe the reason it doesn't work on some OS is due to some core architectural part of how the code is structured such that it would involve a massive refactor in the future if it wasn't fixed early on. Sure, focus on getting it working on your own OS first, but don't lose sight of all the platforms you intend to target.
well dude you need to make it work, a large part of the market is windows 8+, you're wasting your time if your product does not even work inside the main OS'