[
Nope, no errors. They just didn’t appear anymore. Thankfully I didn’t have many macros so setting up new ones was an easy task. I wish you could copy them with in- and outputs somehow …
About Preview 4: Thank you for update! I hoped it made classes, actors and assets available in data table row editor that got introduced recently at it is vital for my project.
[/]
Hi,
Did you rename any of your macro libraries? If so, try calling macro from original name. I can still access created in 4.6.1 on my end, however there seems to be a bug that is only calling libraries on their original name. has been entered as UE-7948.
Were there recent changes to AController::GetNavAgentProperties and APawn::GetNavAgentProperties? Did Navigation get moved into a new module?
Edited:
I deleted my intermediate files and did a full rebuild and I was able to compile. Now I am getting same Assertion failed: InstancedRenderData.InstanceBuffer.GetStride() == sizeof(FInstancingUserData::FInstanceStream error else is getting.
Did you rename any of your macro libraries? If so, try calling macro from original name. I can still access created in 4.6.1 on my end, however there seems to be a bug that is only calling libraries on their original name. has been entered as UE-7948.
[/]
Hi!
No, I didn’t rename it. It was “Macros” from very first second on. But I’m glad you found something to fix.
To fix foliage crashing problem I did was delete my Foliage static assets. If that doesn’t work than just delete anything connected to them like Materials, textures, etc.
[=;194550]
What changed with AI? Event Receive Condition Check and Finish Condition Check are now broken for my decorator BPs…
[/]
Yeah they are also broken for me in 4.7 Preview 4. Epic, what happened there? What should I use instead of these two nodes?
Edit: Ok, I found it its an implementable function now. That’s much worse than before Now I can’t have multible “Finish Condition Check” nodes but only a single return node… That means I have to create a local boolean variable which is returned instead of just connecting different vaviables to different “Finish Condition Check” nodes. And it also means graph get’s ugly because of many different wires going into return node. You should have it work old way until you finally implement possibility to have multible return nodes in functions. Btw, when will be? 4.8?
I dont see problem with Gear VR support on known issues list. I think there a quite a few people who would love to test Gear VR integration, me included.
Any word on a fix for UE-7793? I am a little screwed at moment, had been working fine with 4.7 but upgraded before reading about error. My own fault I guess.
[=;209504]
I dont see problem with Gear VR support on known issues list. I think there a quite a few people who would love to test Gear VR integration, me included.
[/]
I really see as a high priority Gear VR is being demoed everywhere right now in every convention and I can not get any of our builds out there to show is a huge for us. Is there a frame or any way we can get get a build up and running on platform ASAP.
“New Project” UI still adds old 4.7\Samples\StarterContent (and says not optimized for Mobile).
Created a new Blank BP/Mobile/Scalable project, imported MobileStarterContent.upack and loaded Starter Map and everything looks fine in Play/Simulate so far.
Would you consider Mobile Starter Content pack in experimental phase?
[=polemos;210650]
I really see as a high priority Gear VR is being demoed everywhere right now in every convention and I can not get any of our builds out there to show is a huge for us. Is there a frame or any way we can get get a build up and running on platform ASAP.
[/]
They say it is coming, it is confirmed from multiple people in team. They also confirmed it on one of last Twitch broadcasts but nobody was able to get it running, there are no updates in patch notes / preview notes… I have no idea but yes information blackout and lack of documentation is worrying.
Now I can’t have multible “Finish Condition Check” nodes but only a single return node… That means I have to create a local boolean variable which is returned instead of just connecting different vaviables to different “Finish Condition Check” nodes. And it also means graph get’s ugly because of many different wires going into return node. You should have it work old way until you finally implement possibility to have multible return nodes in functions. Btw, when will be? 4.8? 
