@ can I please get a reply about the issue i’m getting please?
What issue are you referring to? Nothing is linked in this post you’ve tagged me in here.
I think he means these, he didn’t tag you, just the bug tracker is not working for him (I have seen other people reporting it too):
https://forums.unrealengine.com/unreal-engine/announcements-and-releases/1598851-unreal-engine-4-22-released?p=1604302#post1604302
https://forums.unrealengine.com/unreal-engine/announcements-and-releases/1598851-unreal-engine-4-22-released?p=1604452#post1604452
That’s interesting, I guess it fell out somewhere. [USER=“4894”][/USER] able to shed any light, so to speak?
Great release! However, I found a bug where if you look all the way down (or even close) using right-click in the model viewer, the camera view will snap to the bottom then go upside-down if you keep moving it.
Please fix, thank you!
Sorry please take a look at my post #104](https://forums.unrealengine.com/unreal-engine/announcements-and-releases/1598851-unreal-engine-4-22-released?p=1604452#post1604452) , its not related to the bug reporter it’s related to the following engine crashes I’m getting after updating my project.
Its a weird bug, which effects lots of people on laptops with rtx cards, can anyone help reproducing the issue, i had no luck. It is a real annoying bug which makes it super difficult to play with rtx features, every time i want to experiment I need to connect my laptop to a monitor.
x86-builds now working with Intel video cards! 
Thank you Epic Team! You are awesome!
with the latest geforce driver, you can now use raytracing features on gtx cards. I tried a scene on my 1080 card which gave 30 fps, I got 60 fps on a 2070 card with the same scene
So am I correct in saying this 4.22 release will only work on window 10 now? Had no luck running it!
I must be the only person still staunchly refusing to upgrade from windows 7 because… well it just works…
Windows XP also works. Also, Windows 3.1 still works. But ain’t nobody wanna work on supporting outdated systems. You either move with the times, or you’ll experience incompatibility issues, not only with UE4, but with everything.
Anyways, theoretically Windows 7 is still supported according to the docs (https://docs.unrealengine.com/en-us/…Specifications), but I don’t really think it’s as tested as the systems of today.
Any ideas why physics objects freak out after upgrading a project from 4.21 to 4.22? Everything worked OK in 4.21, but in 4.22 all the physics objects fly in random directions with great force and leave the map. That doesn’t affect all objects in the map for some odd reason. Was there a significant change in physics/collision detection code?
No reason 4.22 wouldn’t run on Windows 7, which isn’t deprecated yet. Of course, more and more engine features will only work on Windows 10, such as ray-tracing which requires the very latest Windows 10 build.
I have the same problem with an advanced vehicle blueprint, I have upgraded the project from 4.19, I can’t find any solution or fix to this irritating and strange behavior , the vehicle fly instantly from the map with random force and direction when play begin, any help is appreciated…
Same issue here after upgrading to 4.22. I found out that a static mesh component in the vehicle blueprint was colliding with the vehicle SK mesh itself.
I suggest checking your collision setups again.
yes it has to do with some mesh component colliding with the vehicle sk collision itself, but I can’t figure out what collision to choose, all setting are not stable, I wonder where is the bug itself since this problem wasn’t present in the previous versions, it must be some new option or any update in 4.22 that produced this problem.
In my case there’s nothing like that. It’s interesting that if I move those objects a bit outside of the playable area then they act normally. So there must be some object inside the playable area that causes them to freak out. That’s a very odd issue, because nothing like that happened in 4.21.
[FONT=comic sans ms]I found an error in 4.22,my character in Seqeunce will automatically become a dynamic material,and it can’t be deleted.
I can delete them when the Sequence window opens,but when you open the Sequence again, it will still be created automatically.
When I exit the Sequece window at 4.21,Dynamic materials disappear automatically,so I think there is a problem with 4.22.
After hours of debugging, the engine is crashing trying to load a widget with a widget switcher with 9 child’s widgets, removing 6 and saving moving the widget from 4.21 to 4.22 fixes the engine crashing as soon as I add these widgets back and restart my project in 4.22 the engine crashes again.
OK, I finally resolved my issue with physics objecs.
My game is a stealth game so once the player triggers an alarm additional reinforcements get spawned. As an optimisation I pre-spawn all the reinforcements, teleport them outside of level bounds and deactivate them. So that there’s no performance hit when they get spawned at runtime. In 4.21 I spawned them at their spawn points and then called “Set Actor Location” with “Teleport” checked to move them out of bounds. And that apparently caused all the physics objects to freak out in 4.22.
So now I’m spawning them out of bounds directly and physics objects no longer freak out.
So yeah - if something similar happens in your project then check if it’s related to actor movement/teleportation.