![]() It is good to hear the "mobile" protocol is somewhat portable in its design. All it takes is for NEStalgia or Feed on iOS to hit the market and you've got a flock of users coming to your system. Not saying this is going to become a million dollar idea, but you can at least make tens of thousands of dollars after it gains popularity. The entire app store concept is what has helped make Apple a fortune already, and I know a lot of app developers who are millionaires off of a single simple app. Honestly it seems silly that you think that wouldn't work out in your favor. ![]() iAD space, dollar for the app, or 2 dollars + per game, Dantom gets a cut. So you really don't think that targeting iOS users (Casual Gamers) with one of the best Casual Gaming systems (BYOND) isn't going to save the project? Micro transactions is your savior. Long story short: porting the newer Flash protocol will be a lot easier than trying to parse the current DS one. Barring that, this project has a bleak future and may just end up in the open source, which is probably what a lot of users want anyway (but be careful what you wish for as privately we do a lot of stuff here that keeps the whole system stable and I have some serious doubts that it would work without some central maintaining body).Īnyway, didn't mean to derail. So we have some substantial changes that will hopefully affect our finances in a positive manner next year, and that, with the goodwill of the many users here, is what we are going to need to make further updates possible. we are really making next to nothing now and simply porting to new platforms isn't going to solve that problem since most users are still on Windows (that is, if we can't make anything off Windows users, adding in Mac users doesn't really help). That said (and I will make a post on this next month when we get all of our current stuff into public testing). The idea there is that this protocol could then be used for other clients, such as a universal HTML5 one or an iOS etc. What we've tried to do here is create a server-client protocol that is straightforward (at the cost of some efficiency), unlike what we have for the current Windows client. 18000, time stamp 0x4791a7a6, exception code 0xc0000139, fault offset 0x00009cac, process id 0xc98, application start time 0x01d198d98a0832da.The Flash client is very simple (of course it is a limited version of the BYOND UI so that is party responsible). 18000, time stamp 0x4791a7a6, exception code 0xc0000005, fault offset 0x000681cb, process id 0圆d4, application start time 0x01d198f290baa338.įaulting application dreamseeker.exe, version 5.0.508.1287, time stamp 0x55762121, faulting module byondcore.dll, version 5.0.508.1287, time stamp 0x55762044, exception code 0xc0000005, fault offset 0x000313b0, process id 0xf98, application start time 0x01d198dc3a365cca.įaulting application dreamseeker.exe, version 5.0.509.1319, time stamp 0x56901bdd, faulting module d3dx9_43.dll!D3DXCreateTexture, version. 18000, time stamp 0x4791a74c, exception code 0xc0000005, fault offset 0x000d1492, process id 0xf74, application start time 0x01d198f26a8674a8.Ģ) Faulting application dreamseeker.exe, version 5.0.508.1287, time stamp 0x55762121, faulting module MSVCR120.dll, version 5.1, time stamp 0x524f7ce6, exception code 0x40000015, fault offset 0x000a7676, process id 0xcb4, application start time 0x01d198f273dc8038.ģ) Faulting application dreamseeker.exe, version 5.0.508.1287, time stamp 0x55762121, faulting module ntdll.dll, version. 1) Faulting application byond.exe, version 5.0.508.1287, time stamp 0x55762146, faulting module mshtml.dll, version.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |