Pcube wrote on 08/19/11 at 03:08:29:



I am joining to request + annex the Dot's PhysX (exactly PhysTest.u) when it will be ready: replacing physics of existing decos like chairs, barrels, boxes etc.

fortunately most of these things have been addressed and changed already.
The execClientHearSound bug was very tricky to catch, since the cause could not really debugged, but it turned out to be some more or less general issue and seems to happen in various Unreal & UT versions.

The ultra shadows...mmh...indeed seem to cause more damage than good...

Despite the fact that there is no date yet for any new release, thanks for the summary

My 227 request/ wishlist is pretty small, i think the current version did an AMAZING job, something that shows all the beta testing was worth it.
Although not everything escaped the bugtesting, and there's some minor issues and stuff i think should be changed:

• The shadow resolution must be capped, personally i think ultra low / low should be  listed in the menu, and maybe allow an experienced user to tweak the .ini to set it higher res, will make an end to these LOL GAME LAGZ N SHADOWS TEH FUGLY.
• Can the unreal beta stuff be seperated in its own package instead of appended in unrealshare? not only have they given me odd errors before (cannot find unrealshare.translocator wtf?) personally i wouldn't have minded an unrealB.u or something, make it just like with oldweapons.u
• Optional, just nagging here, but the oldweapons mutator is AWESOME, but somewhat a pain to run on individual maps, would it be possible to have some menu/ini way to permanently force-enable a mutator upon running a game? this would greatly help those that miss the old pre 220 sounds, and have no idea how to run mutators.
• Even more optional nagging from me, but detailtextures on meshes look so pretty... i just think (almost) every mesh should have them, not just a few

UED:

• Fix the editor destroying random geometry! whenever i'm copying/vertex editing/exporting a brush, sometimes the editor randomly decides to shift a vertex by 0.0001 uu, creating giant bsp holes, breaking texturing, and... well...poop hits the fan.
  *dots mentioned this was some kind of a floating point calculation error
  
  UT/etc had this issue too, but far less prevalent, atleast in there i can copy paste a brush 10 times, and expect one to go wrong, in 227 it goes wrong half the time!
• Fix exporting to brush .u3d format, some brushes refuse to import anymore, maybe related to the previous brush related problem?

Also, remember the issue with characters in the 'Player Setup' preview window not being scaled correctly.

GreatEmerald wrote on 08/19/11 at 23:15:44:


Select VRikersGame and have fun starting all levels with 12HP Does that happen only to me or is it a common thing? I once heard somewhere that It's because something is wrong with the script of VRikersGame so whenever players has 100HP and save/loads it goes back to 12, well same happens if player with full health goes from one level to another.

Smirftsch wrote on 08/21/11 at 18:39:08:


I'm just pointing out the fact that starting botmatch SP with VRikersGame is not a good idea, the game mode stays same through all levels, unless I've missed something It's possible cuz I had a break from playing being on vacation.

Age wrote on 08/20/11 at 09:09:15:


Use this

Also, the point of this thread is not feature request but reminders to include things which are usually 2 minute fixes.

well, that's a bit tricky. I was told the same. There are supposed to be some problem with sound, but no one was willing or able to explain what exactly the problem is, or even provided any details/logs etc. So I have nothing to work with. Or did you see any reports here in the forum? Maybe you know those people and can tell them to do so?
The very few cases I was told turned out to be some driver problem in the end.
So regarding the number of people without problems it's more likely to be some system/driver specific issue in those cases.
Also, there is always old Galaxy sound system as fallback which is still unmodified (except the reverb fix).

That 227 would modify any windows drivers is pure nonsense. It doesn't work outside the Unreal directory.
Anyone can check this easily with some sort of file tracker or file sniffing tool...

The only sound problems I ever noticed were caused by outdated .ini files - one of them was a funny doppler effect - corrected by removing the given ini and having Unreal rebuild a clean one. The fact that people are willing to blame 227 for Driver corruption shows that they probably know nothing about drivers or the engine. I guess they have distrubed drivers and this interferes with 227.

GreatEmerald wrote on 08/25/11 at 08:32:26:


I don't see how it could change windows settings, any Unreal settings are only stored in the ini files - direct input or not, but even if it takes over a setting temporarily (maybe a behavior like the gamma on OpenGL crash)- that's a setting and no change in any windows files or even replacement of something.
Unreal or the patch do not install anything outside the Unreal directory, these are 2 entirely different things.