FreeGameDev

(forked from viewtopic.php?f=72&t=3443#p34256)

bonifarz {l Wrote}:... some texture errors near glass walls on testchamber, but that could be a driver issue.

Nearly forgot about this one. This occurs with both win32 and win64 builds, only when water refraction is on, but not with RE1.2 using the same settings.
Maybe related to viewtopic.php?f=74&t=3456&p=34363&hilit=refraction#p34363

bonifarz {l Wrote}:

bonifarz {l Wrote}:... some texture errors near glass walls on testchamber, but that could be a driver issue.

Nearly forgot about this one. This occurs with both win32 and win64 builds, only when water refraction is on, but not with RE1.2 using the same settings.
Maybe related to viewtopic.php?f=74&t=3456&p=34363&hilit=refraction#p34363

Maybe I'll try reproducing this at some point to solidify your feedback.

Karoushi {l Wrote}:

bonifarz {l Wrote}:

bonifarz {l Wrote}:... some texture errors near glass walls on testchamber, but that could be a driver issue.

Nearly forgot about this one. This occurs with both win32 and win64 builds, only when water refraction is on, but not with RE1.2 using the same settings.
Maybe related to viewtopic.php?f=74&t=3456&p=34363&hilit=refraction#p34363

Maybe I'll try reproducing this at some point to solidify your feedback.

I can confirm that the same thing happens on Mac OS X (10.6.8, with RE 1.31).

Other than that little issue, everything about 1.3 has been a great improvement.

DNL {l Wrote}:

Karoushi {l Wrote}:

bonifarz {l Wrote}:

bonifarz {l Wrote}:... some texture errors near glass walls on testchamber, but that could be a driver issue.

Nearly forgot about this one. This occurs with both win32 and win64 builds, only when water refraction is on, but not with RE1.2 using the same settings.
Maybe related to viewtopic.php?f=74&t=3456&p=34363&hilit=refraction#p34363

Maybe I'll try reproducing this at some point to solidify your feedback.

I can confirm that the same thing happens on Mac OS X (10.6.8, with RE 1.31).

Other than that little issue, everything about 1.3 has been a great improvement.

Confirmed, I've not been given a reason why as of yet, but I suspect it is due to an engine problem.

DNL {l Wrote}:Other than that little issue, everything about 1.3 has been a great improvement.

Seconded. The refraction glitch is a problem of truly lowest severity, and it is about time to express my gratitude for the wonderful work done with this release.

I find this bug wire I testing my vars mod.

youtu.be/ZGjuy8zSJi0
Galactic Weapon Mod
http://forum.freegamedev.net/viewtopic.php?f=73&t=3507&p=34766#p34766

I am not sure what happens. Is that a bug or a mod error?

qreeves {l Wrote}:Confirmed, I've not been given a reason why as of yet, but I suspect it is due to an engine problem.

Fixed in SVN now as of r4273.

In weapon variables, changing the pistol parameter "Boucing geometry" to on, and "Hit owner" to on then when you shoot yourself in the feet, you transform into a "Ghost"

Sniper-Goth {l Wrote}:In weapon variables, changing the pistol parameter "Boucing geometry" to on, and "Hit owner" to on then when you shoot yourself in the feet, you transform into a "Ghost"

This issue has already been fixed upstream in the subversion repository. Workaround for now is to set the 'pistolselfdmg1' and 'pistolselfdmg2' to something that isn't zero.

Had an issue where the map on my radar (radarstyle 3) was the map from the match before. Forgot to take a screenshot but if it happens again I'll make sure I get one.

When i was making a map, i put a light entity and did a quick calc light, the game gives a error message and freezes up.

Hey, try to check this setting in the edit mode, via F3 → lightmap → lightthreads (or just command: /lightthreads N); and set up value 2 or 1 if you didn't do it yet before.
I fixed this issue by that, even when my CPU has 4 threads. And not just the game kept crashing, but blue screens were showing up pretty often.

Sniper-Goth,
For 1.3 to avoid crashing I had to use 1 lightmap thread as well even though 1.2 worked with 2 threads via hyper threading for me. I do recommend trying 1 lightmap thread.
Cheers

The lightthreads should still work fine in 1.3.1, as they did in 1.2. I have a quadcore and run Lighttreads 4, which works without a problem.

Thanks everyone, it worked.

I don't know if this is or not a bug, but every time that i load this map that im making, i am got a Warning message about too many textures.
Any way to take it off?
Note that i started this map in 1.2..... maybe thats why i am having this issues?

Remove the extra "texture" defines under "texture water" - it's just too many textures in that slot.

Thanks for the help.
Everything is fine now.

Rifle and pistol and smg can not shoot through the small windows.

Another bug, but I do not know how to explain.
How to take a demo and how convert it to video?

Inogord {l Wrote}:Another bug, but I do not know how to explain.
How to take a demo and how convert it to video?

That's not a bug, it's not possible in RE. You must record the demo playback through another program such as FRAPS.

Bug in editor

Inogord {l Wrote}:Bug in editor

heh, that's not a bug either

No bug? ok, how fix it? How make textures on this tetrahedrons?

Inogord {l Wrote}:No bug? ok, how fix it? How make textures on this tetrahedrons?

Lol, not a tetrahedron... ALL surfaces in the Cube 2 editor are, well... modified cubes. Even if you use Q and push in a block's sides so it becomes a triangular prism, the bounding box will still remain a cube.