USDZ File Black on Older Devices and Normal Map artefacts - scenekit

I'm stuck creating USDZ files. I've issues with older devices, basically anything older than the iPhone X, displaying items with artefacts resulting from normal maps and other issues whereby the item appears entirely black.
iPhone X and iPad on ios 12 and 12.1 betas run fine with no normal maps:
iPhone 7 iOS 12 non beta with no normal maps:
When I use normal maps I get the following issue on older devices:
You can download the raw files here: https://drive.google.com/drive/folders/13w4fFTr6EQSUyQeEryxQWp0FcPN-84Ci?usp=sharing
Any help is extremely appreciated <3

Related

Codename one Simulators sizes do not fit within the window

While developing app with codename one with Netbeans IDE, I was running into this issue where the simulators were not usable except iphone 3. If I choose the simulator to be iPhone 5 or 6 or 6 plus, the simulator is so huge and only part of it appears on the screen and I couldn't even scroll.
Is there anyway to make the simulator to fit within the window sizes? I tried on Mac and Windows and I experienced the same result.
Please advise.
Uncheck the Scrollable option under the Simulalator menu. It's on by default since some artifacts might appear during scaling but for large skins there is no alternative.

Tabs on android make the whole screen black

IDE: Eclipse
Desktop OS: Mac
Device : Android 4.0.4
Hi,
last week i sent a new android build to the server, and it updated the jar files i have on my Mac, then i installed the app on LG android 4.0.4 device that i tested before, and was surprised to find some pages display all black.
After investigating a little, i discovered that when i use tabs on any form the form will be displayed black only on android, no problem on simulator nor IOS iPhone 6S.
I looked at the forum and i found similar problem happened a year ago , and the solution was to use "android.asyncPaint=false" temporarily . now this removed the black, but messed all the rendering while navigating between tabs.
So my question is why this happened now? the past three months i was developing and deploying on android without any problem. Did the newest update corrupt something?
Thanks
Sam
Using the android.asyncPaint flag is discouraged as it will fallback into a relatively slow compatibility mode. We are currently investigating some regressions in some rendering optimizations that affect some devices and are in the process of deploying a solution for that.
Please let us know if the issues persist.

Naming launch images without using asset catalog

I'm working on a Universal app (my first app) that runs on both iOS 6 and 7 and I'm creating my launch images now.
I've read the Apple documentation on this area but I find I'm still confused.
For the moment, I'd like to work out how to create and link up all my launch images without using the Asset Catalog, if possible.
I've got most, but not all, of the launch images created and added into the Launch Images area of my project like so:
Portrait Non-Retina (iOS 6.1 and Prior) 768x1004 No image with correct dimensions found
Portrait Retina (iOS 6.1 and Prior) 1536x2008 No image with correct dimensions found
Landscape Non-Retina (iOS 6.1 and Prior) 1024x748 No image with correct dimensions found
Landscape Retina (iOS 6.1 and Prior) 2048x1496 No image with correct dimensions found
Portrait Non-Retina 768x1024 Default-Portrait
Portrait Retina 1536x2048 Default-Portrait#2x
Landscape Non-Retina 1024x768 Default-Landscape
Landscape Retina 2048x1536 Default-Landscape#2x
But I'm puzzled as to how to name the iPad image files that are still missing.
You will not be able to do what you are trying to do by naming alone. If you don't want to use the asset catalog (which totally solves the problem without effort, so why would you not use it????), you will have to set up the Info.plist yourself, as Apple explains here:
In iOS 7, an app can use a different launch image depending on which version of iOS it’s running in. To provide different launch images, add the UILaunchImages key to the Info.plist file and use a dictionary to describe each launch image. To learn more about handling launch images, see “App Launch (Default) Images” in iOS App Programming Guide.
I think you should find the naming conventions in the section called App Launch (Default) Images of Apples documentation for resources

ios6 ios7 xcode4.6 xcode5 dilemma

I was building an app in xcode 4.6 (ios6.1) and everything was fine.
I ran the same code through xcode 5 (ios 7) on an ios7 device and simulator, and I ran into the full screen (status bar included) issue, horizontal scrollview issues, modal viewcontroller issues, et al.
I’m using a navigation controller with the bar turned off. Instead I’m using a custom view to pass for a bar. So the extendedEdge thing isn’t working as well.
I understand that eventually, I’ll have to update my design and implementation accordingly.
Now here’s the dilemma – I ran the app (backed up original code) from xcode 4.6 (ios6) on an ios 7 device, and it’s working absolutely fine. It’s leaving it’s gap for the status bar, and there are no issues at all.
What I can’t understand now is how to proceed?
Will the app be accepted if I continue working on xcode 4.6 with ios6 (since it’s almost finished)?
I’m not able to move to xcode 5, since it has only the latest ios7 as the Base SDK.
I can’t find a legitimate way to add ios 6 sdk to xcode 5 (except copying the 6.1 SDK to the xcode5 package).
And, if I hadn’t downloaded xcode 5 DP (which installs it separately), the mac app store would have updated my xcode 4.6 to xcode 5
Apple still accept applications submit through Xcode 4.6
But consider that you would loose some new functionality like having different icons to each OS version etc.
Moreover, your app won't use the 64-bit processor (it is still compatible but if your app is a game or something like that it is recommended to use it).
I assume that in few months you won't be able to submit apps using the old Xcode.
UPDATE:
For you to be able to use status bar as before (like hidden), in your apps plist file add a row call it "View controller-based status bar appearance" and set it to NO
Just to update people who might be looking for an answer to this -
Apple will only accept apps and updates made with Xcode 5 on iOS 7, effective 1st Feb 2014.

Xcode 4.5 Uploading a iPhone 5 app only

i have a app built in Xcode 4.5 with 4 inch screen/View controllers i built this app just for iPhone 5 as i sent it off to iTunes connect. once it said upload received it showed "Missing Localized Screenshots" straight away.
how can i fix this i have 5 screenshots for iPhone 5 and thats it, but if i was to put screenshots for 3.5 inch screens the message goes and my app will wait for review but the one problem is when i run it on my iPod all the images/buttons are I'ver off the screen or in a different places please help.
are there any ways around this if so i really would appreciate it if you could let me known.
or do you have to develop a applications for both devices iPhone 5 and iPhone 4 now?
hope this all make sense and you guys understand what i mean thank you!
It isn't about the device, but the version of the OS. You can't target an app just at the iPhone 5. You can can target an app at iOS version 6 which includes 4 inch and 3.5 inch screens.
Edited to add
There are many resources about supporting multiple screen sizes in iOS6, one of which is, for example:
How to develop or migrate apps for iPhone 5 screen resolution?

Resources