I am having an issue with my standalone tests. I should start by saying everything runs normal in PIE and this issue started a couple nights ago, but everything was working okay before then.
When I run my game in standalone nearly all of my gravity is lost, as well I also have an issue loading a specific character. The error points to an issue loading the skeletal mesh which makes sense as his weapon is loaded and the only indication visible. I will include a link to a video than shows off the difference between the two. As a test I had created a new level in the same project to see if it was level-side but it is through out the entire project.
In the link, You can see the example of PIE vs Standalone. I hope you guys can help me find a solution. was with me to bare witness, so he might have better insight than I can provide. But also, what info may I provide?
Have you manually adjusted the gravity for the player? Does this occur in a clean, blank project with no additional content? Additionally, which hotfix version of 4.7 are you currently using?
I have altered the gravity on the character but only to increase gravity; so the gravity is stronger but I had not altered it in many months. I will try a blank project and see if my issues are still occuring. I am not 100% on the current 4.7 version but I believe it is the latest version (4.7.6?).
I will try creating a new project and let you know the outcome.
Thank you for the reply!
Yes, everything seems to work fine on a new project;
I’m happy to hear this is working for you now. I will mark this as answered for tracking purposes. If the problem persists, please comment back and I’ll be happy to take another look.
Everything is only working fine on a new peoject not my own;
Ah I see, sorry about the confusion on my end. What happens if you set the gravity to default on your player characters in your project and then run it in the standalone game?
No problem! When I default gravity I am getting even less gravity than before.
Can you send me a copy of the project or a test project that this is occurring in? I haven’t been able to reproduce this on my end thus far.
Sorry its been a while since Ive wriiten back; just want to say its ok to close this question. I still could not find a solution and I know you recommended I upload my project, but I went ahead and began writting the project from scratch in 4.8.2 and couldnt be happy. It was time to do a major optimization amyway and that was the best way I could think of. If this is an issue you guys are cursious about looking into I would still be happy to upload the old project. Otherwise thank you for your replies.
yeah same problems with an old project from 4.2 and earlier…
solution was to recreate from scratch (import code and copying the whole content directory to the new one
Yup, I believe my project was from 4.2 or 4.3; Rewrites can be good though. I was getting 20k(ms) compile times in my old project which was unbearable. Now I am getting 3-4k(ms) on my lowest parent class. At the same time I am able to use all my acquired knowledge to make everything work great.
If you can upload the project that would be helpful, though in truth if you are going to update between engine versions it is best to update incrementally as there are a significant number of changes that have occurred between individual changes, much less a jump like 4.3 to 4.8.2. Workflow changes, standard version to version corruption, changed/altered/removed blueprint nodes, and other changes may lend to the errors you are seeing.
I should note thought that my project had not been recently updated between engines. I had been stable in 4.7 for a while. It just broke out of the blue; so I dont think the issue has to do with the engine version. How should I get this to you?
You can either upload the here or send me the /link to a dedicated FTP copy of your project (such as dropbox) in my PM inbox on the forums. I can then check out what may be occurring.
We have not heard from you in several days. I am marking this as answered for tracking purposes. If you are still experiencing this error, please comment with the requested information.