[=EoinOBroin;303519]
No way- as someone who always wanted to make games but was blocked by barrier of learning code, blueprints have allowed me to do anything I could want, quickly, and very intuitively- they are best thing that has happened to UE4 in my opinion. If stability is issue then just stick to whatever version you have started your project with!
[/]
Using 4.8.0 Preview 4 raises some issues with Overlapping events. It seems that default character controller (capsule shaped) intersecting with a Sphere Collision component (part of a custom Actor) raises enter/leave overlapping events every time character moves inside Sphere.
Is there anything of this sort in 4.8 release bug list? same code (using blueprints) worked in 4.7.6 correctly.
Could you please take a look at UE-15894 for 4.8?
All keyboard Keys are still not mappable to ConsoleKeys and that some keys have no KeyName mappings so we can’t map them easily to game key bindings.
Could you please take a look at UE-15894 for 4.8?
All keyboard Keys are still not mappable to ConsoleKeys and that some keys have no KeyName mappings so we can’t map them easily to game key bindings.
thanks,
[/]
Hi,
This is still currently backlogged and has not been assigned a developer so there is no ETA when this will be looked into further at moment.
@,
Thanks for update, but I clearly think that 1 year after shipping first public release, we should solve all those tiny keyboard “bug”. I already raised an issue in first version as azerty keyb were not handle properly and I’m surprised that not all keys are still not “mappable”. I don’t know difficulties to properly register all keyboard keys, but it’s such a basic features for an game engine that I think it deserve some attention.
If you are that behind, it is most definitely worth it to just upgrade to newest version and redo work- you can copy large amounts of nodes if you really need to, there would definitely be similar problems using only C++ too, they have changed how things work there also. Best thing to do is stick with engine version you started with, migrating is always going to cause some issues, but that is expected!
Not sure if it has been reported, but having consistent crashes when copy/pasting/duplicating groups of static meshes- seems to happen every time I try and do it with more than about 8 meshes selected! Other than that, I’m loving new features
Hate to ask but what ever happened to next gen matinee? I forget what it’s called. I just remember hearing about it months and months ago. What was it called again? Any ballpark guesses as to when we might see it implemented?
[=Godling;305414]
Hate to ask but what ever happened to next gen matinee? I forget what it’s called. I just remember hearing about it months and months ago. What was it called again? Any ballpark guesses as to when we might see it implemented?
[/]
It’s called Sequencer. It is still under development (it’s been in planning for a long time) and there is still a lot of work left. We hope to have a working version by end of year.
I haven’t been able to reproduce this on my end consistently. Do you have specific steps you are taking to duplicate just before this occurs?
[/]
It seems to actually be related to refractive panner window material I had on several meshes- I can copy/duplicate any number of regular meshes, but only seems to happen when that refractive material is applied!
Going through some basic tutorials on level creation. Two issues so far:
Lock actor to object isn’t available (I’ve seen this reported elsewhere)
Geometry alignment doesn’t seem to work, specifically “Align surface planar”. other options don’t seems to do anything either.
(Edit - one more issues)
Viewport exposure override (setting to manual +1) didn’t stick after a reload of project. It reset back to “Auto”
I’m eager to work today and dont want to progress since I dont have a stable version of editor to go with right now, both 4.7.6 and 4.8.0 giving me issues.