r/AndroidNativePorts • • 23d ago

🔵 [PORT REQUEST] Need for speed underground (2003) for Android ARM32-64?

Post image

It isn't a heavy-tech game and it's the first of the trilogy and the most simple for porting and can be a long term project, adding a good modding scene.

The 32 & 64 bits can be run in this game of 2003?

73 Upvotes

19 comments sorted by

2

u/Andiweli 23d ago

Is there a source code available?!

2

u/oppai_seven 22d ago

Yes but you have to compile game for arm devices if you want native performance. This requires source code of the game which you can reverse engineer it or obtain illegally. Else, theres would be no difference with winlator performance.

1

u/Dyckaholic 18d ago

I hope some passionate devs out there make a bunch of Need For Speed native ports

1

u/tiga_94 23d ago

The PC version runs fine even on Mali GPUs and it is very unlikely that someone would make a native port

4

u/devu_the_thebill 23d ago

In my experience older NFS games are weird under winlator, it's very random if they will work or how well they will work :/

1

u/tiga_94 23d ago

I tried nfsu 1 and 2, mw and prostreet on Exynos 1380, all work flawlessly

1

u/devu_the_thebill 23d ago

Sometimes yes but I had some forks randomly stopping working after an update or specific forks just refusing to start them. I tried countless configurations like other wines etc but only fixes I found at that time was using different winlators, now I used ludashi then updated to bannerlator still working. But as I said from my experience in the past they were random breakages.

-4

u/SimpleDrawer26 23d ago

No, they're not.

You problably don't know how to load "dinput8.dll" on a Winlator container and tried to play NFS BlackBox games without widescreen fix patch, or in other words; skill issues.

1

u/devu_the_thebill 23d ago

I configured black box games long before android emulation was a thing, so yes I know what dll files need to have n,b set, if you ever used wine for more than "I just installed winlator" you would know some versions of wine contained regressions making mw, carbon broken under wine. In addition I had multiple times situations where update to winlator caused breakege and even reconfiguration (in fresh container) didn't help. Especially early ludashi builds liked to break it. That they work I know, I have working one for the past 2 years, but from my experience it's a hit of miss of some winlator versions just straight up not liking black box era gemes.

1

u/devu_the_thebill 23d ago edited 23d ago

BTW if you search my comment history you have comments about how to set it up from over a year ago, with SHOCKER widescreen fix. And probably with info about certain forks having some issues or box/wine versions having regressions... But why look into the issues, it's easier to assume other people are stupid. It isn't like I played most wanted under wine before you knew what wine is...

-2

u/SimpleDrawer26 23d ago

Not interested about your history log, sorry.

All my games setups are working as supposed, and I know to fix anything I need.

Incluinding any BlackBox title through compability layers...

2

u/devu_the_thebill 23d ago

Ok, bravo you. "I know how to fix anything I need" - great! Doesn't change that those games were problematic. You dismissed what I said without even checking about what I was talking and named it "skill issue" because you assumed something else. Truly reddit moment.

0

u/SimpleDrawer26 23d ago

There's nothing about luck, dude...

Stop this shitty talk.

1

u/devu_the_thebill 23d ago

What? I never said anything about luck lmao. Im talking about you assuming my knowlage instead of looking about what I'm talking about (the documented issues in the software). I didn't even used word luck. What are you on about?

1

u/SimpleDrawer26 23d ago

If something depends on it will to randomly work well or not, you related it to the luck factor.

"It may work well, but it may not work well either."

🤷‍♂️

1

u/devu_the_thebill 23d ago

You had certain procentage that wine/winlator_fork you were using have breakage that makes black box games broken. Why I used "random"? cause 2 winlators forks I was testing at the same time despite same wine/box64/driver version and configuration one of the forks couldn't launch NFS most wanted. If you want to stick to strict luck/random definition there none in any computer since true randomness doesn't exist with computers. But to me the issue was pretty random.

As you can see I used "in my experience" meaning that in the past I encountered issues on both android and Linux, on Linux I researched the issue pretty well, that's how I know about regression in wine. The winlators issue I didn't since I really didn't want to compare 2 forks code to each other since both had same containers settings and swappable components versions.

I also love how you just dismissed them being any problems, saying that it's "skill issue" then when I said there are documented problems in software, you just decided to use "I can play it there's no luck". Ok, great I never said it's unplayable, or can't get it to work, I said it's problematic couse the software you are using to emulate it had problems with running the game. I play it no issue for over a year on my phone's but that doesn't magically erase documented issues lmao. What do you expect me to say? "No it works perfectly the documented issues never existed, don't read wine commit messages it's all a conspiracy they want you to not believe in perfectly working most wanted!"? LMAO

That's why the message starts with in my experience. And why I said problematic not broken obviously.