Skip to content
This repository has been archived by the owner on Jan 22, 2021. It is now read-only.

Support Unicode Games #50

Open
2217936322 opened this issue Jul 17, 2019 · 6 comments
Open

Support Unicode Games #50

2217936322 opened this issue Jul 17, 2019 · 6 comments
Assignees
Labels
feature request Request to add new feature

Comments

@2217936322
Copy link

image
https://drive.google.com/open?id=1br-HVzIwMyQDZ57fZ3prn8fLAXwh1Zpo
thx

@CorrM
Copy link
Owner

CorrM commented Jul 17, 2019

this game use Unicode chars for a loot of stuff.
for now i can't do any thing. will need to recode a lot of stuff to fit that.

@CorrM CorrM self-assigned this Jul 17, 2019
@CorrM CorrM changed the title Crash Support Unicode Games Jul 17, 2019
@CorrM CorrM added the feature request Request to add new feature label Jul 17, 2019
@wallopthecat
Copy link

wallopthecat commented Aug 29, 2019

edit nvm

@CorrM
Copy link
Owner

CorrM commented Aug 29, 2019

@wallopthecat it's need to edit the uft src. to support Unicode var names and other stuff like that.

@fake-cheater
Copy link

nice job

@boboben1
Copy link

boboben1 commented Dec 4, 2019

I found an easy fix for it, albeit not perfect, and that is to continue on failures rather than breaking in ObjectStore.cpp in function bool ObjectsStore::ReadUObjectArray() This fixed it for me in Ace Combat 7 (getting the same error) and an SDK generated. Some objects in the GObjects array were in PAGE_GUARD pages. I haven't yet tested the accuracy of the generated SDK, mind you, but it appears to be fine.

Such a small change, I didn't feel a pull request was warranted.
Changed:

			if (Utils::MemoryObj->IsStaticAddress(dwUObject) || !ReadUObject(dwUObject, *curObject))
				break;

to

			if (Utils::MemoryObj->IsStaticAddress(dwUObject))
				break;

			
			if(!ReadUObject(dwUObject, *curObject))
				continue;

@CorrM
Copy link
Owner

CorrM commented Dec 5, 2019

@boboben1 Thanks for that hel. i will submit that in the UFT.Net

@CorrM CorrM closed this as completed Feb 9, 2020
@CorrM CorrM reopened this Feb 9, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature request Request to add new feature
Projects
None yet
Development

No branches or pull requests

5 participants