Android part 2

For new and upcoming OpenMW branches and ports; move fast and break things!
Laicus
Posts: 21
Joined: 29 Apr 2018, 08:35

Re: Android part 2

Post by Laicus » 17 Apr 2019, 05:41

Tecumseh1976 wrote:
17 Apr 2019, 01:58
Has anyone had any luck getting changes to cfg files to stick? I have tried everything I can think of to add esp files.
ESP / ESM files are added to the openmw.cfg file after the lines with the names of the main ESM:
content = Morrowind.esm
content = Bloodmoon.esm
content = Tribunal.esm
content = MOD1.esm
content = MOD2.esp

BSA archives are added at the beginning of the openmw.cfg file, also after the lines with the name of the main archives:
fallback-archive = Morrowind.bsa
fallback-archive = Tribunal.bsa
fallback-archive = Bloodmoon.bsa
fallback-archive = MOD1.bsa

Tecumseh1976
Posts: 10
Joined: 30 Mar 2019, 11:06

Re: Android part 2

Post by Tecumseh1976 » 17 Apr 2019, 14:16

Yep tried that countless times and ways... as soon as I launch the game it goes away.

content=Morrowind.esm
content=Bloodmoon.esm
content=Tribunal.esm
content=Better_heads.esm

reddragon72
Posts: 17
Joined: 06 Apr 2019, 20:11

Re: Android part 2

Post by reddragon72 » 17 Apr 2019, 18:58

Tecumseh1976 wrote:
17 Apr 2019, 14:16
Yep tried that countless times and ways... as soon as I launch the game it goes away.

content=Morrowind.esm
content=Bloodmoon.esm
content=Tribunal.esm
content=Better_heads.esm
the entries go away in the file? If so try this build https://github.com/xyzz/openmw-android/ ... 2019-04-01

pulion
Posts: 15
Joined: 26 Dec 2018, 07:45

Re: Android part 2

Post by pulion » 17 Apr 2019, 19:29

Is there any way to fix the memory leak problem? Or is this a common problem of OpenMV, and not just the port on the android?

Tecumseh1976
Posts: 10
Joined: 30 Mar 2019, 11:06

Re: Android part 2

Post by Tecumseh1976 » 17 Apr 2019, 20:53

reddragon72 wrote:
17 Apr 2019, 18:58
the entries go away in the file? If so try this build https://github.com/xyzz/openmw-android/ ... 2019-04-01
That is the build I have been using. Thank you for the suggestion though.

thephantomfiddler
Posts: 13
Joined: 06 Mar 2019, 01:03

Re: Android part 2

Post by thephantomfiddler » 20 Apr 2019, 00:24

Can we get an update to SDL 2.0.9? That may fix the black screen on resume issues.

xyzz
Posts: 87
Joined: 14 Jan 2018, 22:25

Re: Android part 2

Post by xyzz » 20 Apr 2019, 04:38

thephantomfiddler wrote:
20 Apr 2019, 00:24
Can we get an update to SDL 2.0.9? That may fix the black screen on resume issues.
The black screen on resume has nothing to do with sdl, it's happening because when an android application is minimized the opengl context gets lost and needs to be recreated (which includes reloading all textures and etc)

gc168
Posts: 2
Joined: 20 Apr 2019, 11:38

Re: Android part 2

Post by gc168 » 20 Apr 2019, 11:48

Hi all, new user of Android app and it's been amazing! Still can't believe this works at all on a phone :D
If I found an issue/bug, do I post it here or start a new thread? Thanks in advance.

thephantomfiddler
Posts: 13
Joined: 06 Mar 2019, 01:03

Re: Android part 2

Post by thephantomfiddler » 20 Apr 2019, 17:51

xyzz wrote:
20 Apr 2019, 04:38
thephantomfiddler wrote:
20 Apr 2019, 00:24
Can we get an update to SDL 2.0.9? That may fix the black screen on resume issues.
The black screen on resume has nothing to do with sdl, it's happening because when an android application is minimized the opengl context gets lost and needs to be recreated (which includes reloading all textures and etc)
So right now, other than stability (and potentially more controller support because of SDL Android supporting hidapi), there really isn't anything with updating to the latest SDL currently?

xyzz
Posts: 87
Joined: 14 Jan 2018, 22:25

Re: Android part 2

Post by xyzz » 20 Apr 2019, 19:49

gc168 wrote:
20 Apr 2019, 11:48
Hi all, new user of Android app and it's been amazing! Still can't believe this works at all on a phone :D
If I found an issue/bug, do I post it here or start a new thread? Thanks in advance.
You can post them here but make sure it's not been reported before.
thephantomfiddler wrote:
20 Apr 2019, 17:51
xyzz wrote:
20 Apr 2019, 04:38
thephantomfiddler wrote:
20 Apr 2019, 00:24
Can we get an update to SDL 2.0.9? That may fix the black screen on resume issues.
The black screen on resume has nothing to do with sdl, it's happening because when an android application is minimized the opengl context gets lost and needs to be recreated (which includes reloading all textures and etc)
So right now, other than stability (and potentially more controller support because of SDL Android supporting hidapi), there really isn't anything with updating to the latest SDL currently?
I'm not aware of any stability issues with our SDL either; the problem with updating is that they break compatibility with the Java API in every minor release (such as 2.0.8=>2.0.9), and this basically requires me to spend a few hours doing a manual three-way merge of our SDL2 Java code. Also, every time they change controller-related stuff in SDL code, this requires me to go through my gamepad emulation code and fix it (and PR to openmw since that's where the bulk of the code lives), which again I'd rather not do unless there are real massive improvements in the new version.

Post Reply

Who is online

Users browsing this forum: Laicus, xyzz and 1 guest