EDuke32 2.0 and Polymer! "talk about the wonders of EDuke32 and the new renderer"
#3805 Posted 25 May 2013 - 08:53 AM
#3806 Posted 25 May 2013 - 09:52 AM
Mateos, on 24 May 2013 - 09:19 AM, said:
Firewall blocked the program demanding a confirmation to allow it to do something just a little too late. Setting it manually solved the problem.
#3808 Posted 25 May 2013 - 02:04 PM
- "Version Mismatch" for savegames saved with r3813
- On the automap, the levelname is shown together with the 3DR par times, e.g. for E1L1 "00:53 Hollywood Holocaust"
- At least menu tiles 2502/2503 ("Atomic") don't show up any more.
Everything works with r3814 or earlier.
Additionally, I have noticed lately that flickering forcefields turn black while being invisible. See screenshots below. This is with Polymer 32-bit (at least, dunno about the rest) and has been going on for a few builds already as far as I can tell. I have posted my settings here already in case they are needed.
This post has been edited by NightFright: 25 May 2013 - 02:31 PM
#3809 Posted 25 May 2013 - 02:51 PM
#3810 Posted 27 May 2013 - 09:53 PM
If it were possible in the technical programming side, I could think a few ways to easily navigate and such... considering that smartphones are getting bigger and stronger everyday.
If you disagree I'd like to know why, yeah you
This post has been edited by DavoX: 27 May 2013 - 10:05 PM
#3811 Posted 27 May 2013 - 10:24 PM
DavoX, on 27 May 2013 - 09:53 PM, said:
If it were possible in the technical programming side, I could think a few ways to easily navigate and such... considering that smartphones are getting bigger and stronger everyday.
If you disagree I'd like to know why, yeah you
It’s not practical nor would the touch screen be accurate enough to work with Mapster. It would be extremely frustrating on a portable device not to mention mapster uses all 104 keys on a keyboard. It would take you 100 years to make one map. It’s hard enough to use Mapster on a laptop with a track pad let alone a mobile touch screen a quarter of the size.
Some things just don’t work well on mobile devices and this would be one of these cases. Even if they did try to develop it for the mobile devices the frame rate would suck because the majority of these mobile devices use ARM based processors. I’m pretty sure the source code requires X86 architecture. They would have to rewrite the entire program just to make it work with ARM processors and they just don't measure up when it comes to performance for complex applications making it not worth the while. As for today's tablets which make use of Intel's X86 processors I still think there would be a huge agrevation factor of trying to map on a small minature device stylus pen or not.
It would be worse than running Eduke with an ATI video card & AMD processor if you can imagine that. I mean common who does that? LOL
This post has been edited by Paul B: 27 May 2013 - 11:14 PM
#3812 Posted 28 May 2013 - 04:34 AM
About the keys and such, I was thinking that some people use smartphones as pcs connecting keyboards and even mouses to them, I dunno.
Well, doesn't hurt to ask
#3813 Posted 28 May 2013 - 04:38 AM
#3814 Posted 28 May 2013 - 09:30 AM
#3817 Posted 28 May 2013 - 11:22 AM
Diaz, on 28 May 2013 - 09:42 AM, said:
Yea very shocking. The developers must be doing it for the experience and the challenge of making it cross platform. I can't even see anyone even attempting to use it on a wii. That's just strange. I wonder if anyone other than the developers will use the wii version? I just can't see it catering to a very big audience on those platforms. I have a Wii i never use, now this might give me a reason to use my wii and see how well it works. lol
This post has been edited by Paul B: 28 May 2013 - 04:12 PM
#3818 Posted 28 May 2013 - 12:22 PM
My post was more to say that
Paul B, on 27 May 2013 - 10:24 PM, said:
isn't necessarily correct, and
Paul B, on 27 May 2013 - 10:24 PM, said:
is completely wrong.
Keep in mind that Android means large tablets in addition to smartphones, and smartphone screens are getting both bigger and denser. Combine that with a hardware keyboard as DavoX said and you're approaching mappability. Maybe add some multi-touch gestures to make up for the keyboard.
Yes, the Mapster32 Wii build is essentially for novelty. I wasn't concerned with it myself, but to my surprise people requested it. Go figure.
#3819 Posted 28 May 2013 - 12:36 PM
#3821 Posted 28 May 2013 - 01:09 PM
Attached File(s)
-
working.log (12.55K)
Number of downloads: 548 -
broken.log (13.31K)
Number of downloads: 565
#3823 Posted 28 May 2013 - 01:30 PM
#3824 Posted 28 May 2013 - 02:03 PM
Still surprised to see FPS dip into low 20ies at time, on a pretty high end PC. Are there any performance improvements planned to the polymer renderer?
#3826 Posted 28 May 2013 - 03:08 PM
Sorry Hendricks266, I don’t agree with you. Of course the mobile computing has dramatically improved but I believe mobile computing serves a small and limited purpose. For instance, my smart phone I use to check my e-mail but you will never see me button mash to create an e-mail and send it from my phone its a waste of time. I do not believe desktop applications such as map editors should migrate to portable miniature devices just to keep up to a trend. I also believe this mobile trend is a fad and I’ll be glad when the focus comes back to PC. In my opinion it’s a waste of freakin’ resources and time to fulfill what purpose? So that 2 or 3 people who can't sit in front of their computer can lay on their bed and map edit with a stylus? I am not on board with this idea as this software will never be a good fit for mobile computing and it’s a waste of time pursuing. Unless you plan on turning Eduke into a flash player based game and redoing the entire mapster interface into a drag and drop system.
Just a thought, maybe you could incorporate Mapster to work with Siri voice recognition. Then we could pump out Duke Nukem maps with dictation on mobile devices. Now that would be kick ass!
"Siri build sector by X, Y & Z coordinates! use floor tile 773 and wall tile 878". That could actually make things faster instead of using touch, keyboard and mouse functions to some degree.
This post has been edited by Paul B: 28 May 2013 - 04:17 PM
#3827 Posted 28 May 2013 - 03:17 PM
Mr.Flibble, on 28 May 2013 - 02:31 PM, said:
Whenever this is explained, it should always be clarified that it's ATI/AMD's fault for making bad drivers, not ours for being deficient as a program. We already have workarounds in place for ATI's problems but we can't work around everything.
#3828 Posted 28 May 2013 - 03:24 PM
This post has been edited by Paul B: 28 May 2013 - 04:16 PM
#3829 Posted 28 May 2013 - 04:46 PM
Hendricks266, on 28 May 2013 - 03:17 PM, said:
Yes. I should have mentioned that. You are correct. Although, I think my link to NVidia's web site was a kind of sarcastic way of saying that.
#3830 Posted 28 May 2013 - 05:54 PM
Paul B, on 28 May 2013 - 03:08 PM, said:
Sorry Hendricks266, I don’t agree with you. Of course the mobile computing has dramatically improved but I believe mobile computing serves a small and limited purpose. For instance, my smart phone I use to check my e-mail but you will never see me button mash to create an e-mail and send it from my phone its a waste of time. I do not believe desktop applications such as map editors should migrate to portable miniature devices just to keep up to a trend. I also believe this mobile trend is a fad and I’ll be glad when the focus comes back to PC. In my opinion it’s a waste of freakin’ resources and time to fulfill what purpose? So that 2 or 3 people who can't sit in front of their computer can lay on their bed and map edit with a stylus? I am not on board with this idea as this software will never be a good fit for mobile computing and it’s a waste of time pursuing. Unless you plan on turning Eduke into a flash player based game and redoing the entire mapster interface into a drag and drop system.
Just a thought, maybe you could incorporate Mapster to work with Siri voice recognition. Then we could pump out Duke Nukem maps with dictation on mobile devices. Now that would be kick ass!
"Siri build sector by X, Y & Z coordinates! use floor tile 773 and wall tile 878". That could actually make things faster instead of using touch, keyboard and mouse functions to some degree.
Paul he's obviously making fun of my post. I guess you didn't turn on your sarcasm detector
#3831 Posted 28 May 2013 - 06:11 PM
DavoX, on 28 May 2013 - 05:54 PM, said:
Me? I'm completely serious about Mapster32 Wii.
http://svn.eduke32.c...er32_meta_1.xml
http://svn.eduke32.c...er32_meta_2.xml
#3832 Posted 28 May 2013 - 06:29 PM
(was using the torque 3d engine, which might've had a part in it being bad)
This post has been edited by DavoX: 28 May 2013 - 06:31 PM
#3833 Posted 28 May 2013 - 07:22 PM
DavoX, on 28 May 2013 - 06:29 PM, said:
(was using the torque 3d engine, which might've had a part in it being bad)
Even playing games on the Wii can be a painful process lol Watch out for my flying remote the wrist strap is for noobs.
This post has been edited by Paul B: 28 May 2013 - 07:24 PM
#3834 Posted 29 May 2013 - 04:42 AM
Hendricks266, on 28 May 2013 - 06:11 PM, said:
http://svn.eduke32.c...er32_meta_1.xml
http://svn.eduke32.c...er32_meta_2.xml
So eDuke DOS was an April Fool's joke but Mapster32 Wii isn't?

Help
Duke4.net
DNF #1
Duke 3D #1


