Announcement

Collapse
No announcement yet.

Need help with building for iOS...

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • replied
    Originally posted by NilsonLima View Post

    You can just go to the first post and click on Edit button at that post and change the title. It might show an error, but the title does get changed.
    Yay it worked... Thanks a lot... I was feeling negative about the negative feeling of that title...

    Leave a comment:


  • replied
    Originally posted by Bernessas View Post
    BTW, is there any way to change the title of this discussion?
    You can just go to the first post and click on Edit button at that post and change the title. It might show an error, but the title does get changed.

    Leave a comment:


  • replied
    Antidamage ANameTooLongToFi Dannington I really need help. No matter what I try, I have not been able to get precomputed visibility to work in the iOS build. When I use Showflag.PrecomputedvisibilityCells 1 I can see the cells but they don't actually do anything... I know this because of what happens when I use FreezeRendering.

    Leave a comment:


  • replied
    BTW, is there any way to change the title of this discussion?

    Leave a comment:


  • replied
    Hi Antidamage . I have now confirmed it.
    I uninstalled Unreal from my mac, then reinstalled it.

    I brought the test project over from my pc again and built the lighting on the mac.

    Once the precomputed visibility actually worked on mac but after I had built it for iOS and installed it on my iPhone 6 it once again didn`t work.

    Is this something wrong with the engine or am I missing some setting that needs to be enabled when one builds on mac?

    I have been unable to find any reference to any problem like this with my wording in searches.

    I also did a test with a new, clean, first person starter map in a clean unreal project that I started directly on my mac. In the project on the mac precomputed visibility doesn't work from the start. And also not in the packaged build that I installed on my iPhone 6.

    Leave a comment:


  • replied
    YUP!

    Precomputed visibility IS NOT WORKING... any idea why that would be? I just built lighting again.

    I then started play in a new editor window and ran the console command FreezeRendering.

    In game I walked over to where I know nothing should be rendered but there they all were... Objects that are completely occluded when the level starts... all rendered...
    Attached Files

    Leave a comment:


  • replied
    Hi guys... This discussion is getting quite interesting and a bit over my head... Haha...

    I think I have found what is causing the terrible FPS that I have experienced.

    Precomputed visibility...

    It does not work at all in the project that I take from my PC over to my mac for building. This is even though it is all set up correctly and working perfectly on my pc.

    I am now building AGAIN on the mac to make sure and then I will test again.

    Leave a comment:


  • replied
    Yes, you need the privacy policy URL. They consider going on to Testflight to be step 1 in releasing.

    Just use this: https://www.gdprprivacynotice.com/

    Leave a comment:


  • replied
    Originally posted by Antidamage View Post
    TestFlight is trivial as long as you're building on a Mac. iOS in general is pretty much terrible beyond the blueprint development stage if you're using Windows.
    I think I may have found out the problem, and it's a real face-palm. For some reason I was sure I needed to use an ad-hoc distribution profile, which UE won't build with - it kept coming up with errors like 'can't sign' etc. I jumped though massive hoops including resigning ipa's - and just a few moments ago got an email from apple saying - 'hey, you should be using an app store distribution profile - don't use an ad-hoc one'. I feel pretty stupid now! I'm not going to celebrate yet though - i'm sure there are a ton of other irritations to get through. - Do you know if you need the Privacy Policy URL if you're just testing?

    Dan

    Leave a comment:


  • replied
    TestFlight is trivial as long as you're building on a Mac. iOS in general is pretty much terrible beyond the blueprint development stage if you're using Windows.

    Leave a comment:


  • replied
    Originally posted by Antidamage View Post
    Just as an aside the entire point of the tick delta property is to get consistent behaviour over different frame rates. Set up a coefficient of force, inertia or smoothing and then multiply it by the tick delta, then adjust your coefficient again to get the result you wanted.

    If you're using AddImpulse however this already takes the tick delta into account and you don't want to double up on that.

    Thanks - the objects you move sort of slide as you drag your finger. There's no physics between your finger and the object - the object imparts movement to other objects in the scene. There's just an interp to BP on the slid object. This is so you can massively jerk the object. I've noticed a massive jerk can happen if there's a framerate hitch though.

    This is the same with my camera manager which orbits the scene with a finger drag.

    Anyway - it works quite well at the moment. My main problem is with testflight now. I think i've managed to re-sign the ipk file (it uploaded to App Store Connect anyway). Now I just have to jump through a million hoops which I didn't expect when someone told me that testflight was easy! I'm just writing a Privacy Policy which I have to host somewhere apparently.

    Also! My original project name had an underscore character in, which was another fail with the app store connect uploader.

    Leave a comment:


  • replied
    Just as an aside the entire point of the tick delta property is to get consistent behaviour over different frame rates. Set up a coefficient of force, inertia or smoothing and then multiply it by the tick delta, then adjust your coefficient again to get the result you wanted.

    If you're using AddImpulse however this already takes the tick delta into account and you don't want to double up on that.

    Leave a comment:


  • replied
    Originally posted by Bernessas View Post

    Please tell me why you made all of your materials unlit...
    Framerate went from a shakey 25-35, sometimes dropping hitching below 20, to a solid 60fps (where it's capped) with no drop below. Mine's a physics based game so it's way better at a solid 60fps, and also, my camera contol system and object pulling uses some delta tick stuff for smoothing which hates spikes. Also my iPad's battery lasts way longer running unlit.

    Still struggling with distribution provisioning. It seems no matter what I do there are problems with signing. I'm just looking at some re-signing tools so I can change the provisioning and cert from Dev to Dist once it's built.

    Leave a comment:


  • replied
    Originally posted by Dannington View Post
    Hi - i'm going to slightly piggyback off this! I've been asked to make a build of my game for iPad - this was all fine once i'd made all my materials unlit etc...
    Please tell me why you made all of your materials unlit...

    Leave a comment:


  • replied
    You need to select 'Shipping' and 'For Distribution' in the packaging tab of project settings.

    Yes you need to make a distribution certificate AND a distribution provisioning profile. They both change when you build for Testflight.

    Jump on the website and make them, then go to XCode account prefs and click "download manual profiles" to acquire them. Then reload UE and start using them. Make sure you name them something obvious like "Testflight Provision" and "Testflight Cert".

    Leave a comment:

Working...
X