Rank: Forza Staff
#1 Posted : Tuesday, July 9, 2019 7:20:28 AM(UTC)
FH4 Release Notes: July 9th, 2019
Nitro Glitter
https://support.forzamotorsport.net/hc/en-us/articles/360026131334-FH4-Release-Notes-July-9th-2019

Quote:
We're constantly working to improve the experience in Forza Horizon 4. Below you will find a summary of items fixed or improved upon in this content update.

Version Number
PC: 1.336.17.2
Xbox: 1.326.25.0
This update is to fix a crash on the front end when the users language is set to Traditional Chinese.


Download size:
155.7 MB on Xbox One X

Edited by user Tuesday, July 9, 2019 6:47:34 PM(UTC)  | Reason: Not specified

Community Manager | ManteoMax.com Forza spreadsheets
Rank: R-Class Racing License
 2 users liked this post.
#2 Posted : Tuesday, July 9, 2019 8:56:07 AM(UTC)
1 Chinese fix???

So we still see through the houses then... that's not important?

You still set a marker position on the map, but it never goes away.. not important?

Just two of the latest bugs to make it into Forza!

Not to mention the 6 month old bugs.

Edited by user Tuesday, July 9, 2019 8:57:59 AM(UTC)  | Reason: Not specified

Rank: C-Class Racing License
 3 users liked this post.
#3 Posted : Tuesday, July 9, 2019 8:58:42 AM(UTC)
Quote:
1 Chinese fix???

So we still see through the houses then... that's not important?


Read past the Chinese mate - it's a game crash bug. Of course it's way more important than seeing through houses as it's a critical bug (in other words - using the product is impossible) as opposed to convenience bug (e.g. experience can be affected for a limited number of users in specific scenarios).
PTG Quadro40k



My Youtube Channel
Rank: R-Class Racing License
#4 Posted : Tuesday, July 9, 2019 9:00:54 AM(UTC)
I know but in reality the fixes should take 5 minutes so what's the difference? Moving a camera doesn't take several weeks.

Edited by user Tuesday, July 9, 2019 9:01:49 AM(UTC)  | Reason: Not specified

Rank: A-Class Racing License
 2 users liked this post.
#5 Posted : Tuesday, July 9, 2019 9:05:13 AM(UTC)
This isn’t about those bugs tho, this is about a bug that crashes the game for some users. Seeing through houses and a map marker just don’t take precedent over it. Sorry if those 2 minor things somehow make the game unplayable for you.
Rank: C-Class Racing License
 4 users liked this post.
#6 Posted : Tuesday, July 9, 2019 9:05:55 AM(UTC)
Quote:
I know but in reality the fixes should take 5 minutes so what's the difference?


I highly doubt anything related to code in the game of this size takes 5 minutes.
PTG Quadro40k



My Youtube Channel
Rank: R-Class Racing License
#7 Posted : Tuesday, July 9, 2019 9:17:33 AM(UTC)
Originally Posted by: Quadro40k Go to Quoted Post
Quote:
I know but in reality the fixes should take 5 minutes so what's the difference?


I highly doubt anything related to code in the game of this size takes 5 minutes.


You don't look through the entire code. You look through the bit that puts the camera in the house which should be in a subroutine linked to houses jumping to Position Camera. How hard is that?

Edited by user Tuesday, July 9, 2019 9:18:48 AM(UTC)  | Reason: Not specified

Rank: S-Class Racing License
 2 users liked this post.
#8 Posted : Tuesday, July 9, 2019 9:36:25 AM(UTC)
Originally Posted by: AquaPainter168 Go to Quoted Post
You don't look through the entire code. You look through the bit that puts the camera in the house which should be in a subroutine linked to houses jumping to Position Camera. How hard is that?

In perfectly written code it would be that easy, but what happens is people are put under constant pressure to deliver short terms results, and long term code quality suffers.
Rank: R-Class Racing License
 1 user liked this post.
#9 Posted : Tuesday, July 9, 2019 10:29:16 AM(UTC)
Originally Posted by: breeminator Go to Quoted Post
Originally Posted by: AquaPainter168 Go to Quoted Post
You don't look through the entire code. You look through the bit that puts the camera in the house which should be in a subroutine linked to houses jumping to Position Camera. How hard is that?

In perfectly written code it would be that easy, but what happens is people are put under constant pressure to deliver short terms results, and long term code quality suffers.


You're not writing code for 1 program though, you are writing code for all Forza versions, so you think about Forza 5, and you think also about Forza 6. The code will be passed along, so taking your time over it is worth millions of pounds. Having bugs loses customers. Nobody should be writing code that they can't read later. Besides which the camera bug was probably to position a player in a Lego car, so it's also traceable back to when that happened.

Edited by user Tuesday, July 9, 2019 10:32:59 AM(UTC)  | Reason: Not specified

Rank: S-Class Racing License
 1 user liked this post.
#10 Posted : Tuesday, July 9, 2019 9:12:03 PM(UTC)
Originally Posted by: AquaPainter168 Go to Quoted Post

You don't look through the entire code. You look through the bit that puts the camera in the house which should be in a subroutine linked to houses jumping to Position Camera. How hard is that?


And then you miss another bit of code that calls that subroutine in such a way that the fix creates a new problem. And that sort of thing inevitably happens even when you're being careful, much less when you're rushing it in five minutes.
Welcome to the Hyperbolic Whine Chamber. If you cry hard enough you might get your pouter level over 9000.
Rank: R-Class Racing License
 1 user liked this post.
#11 Posted : Wednesday, July 10, 2019 4:59:37 AM(UTC)
Originally Posted by: Ti Hsien Go to Quoted Post
Originally Posted by: AquaPainter168 Go to Quoted Post

You don't look through the entire code. You look through the bit that puts the camera in the house which should be in a subroutine linked to houses jumping to Position Camera. How hard is that?


And then you miss another bit of code that calls that subroutine in such a way that the fix creates a new problem. And that sort of thing inevitably happens even when you're being careful, much less when you're rushing it in five minutes.


No, that's called a bodge, you don't do bodges if you program properly. What should simply happen is that XYZ are 3D locations for the camera, and you pass those to the camera_setup(x,y,z)

If you bodge the fix you might put (These are just imaginary examples)...

z= z -10

somewhere in the code, and confuse everyone.

Whereas what you should do is put the -10 in the place where the original code was.

when leaving the code you should clear x y z

X = 0
Y = 0
z = 0

so that other parts of the program aren't altered by using X,Y,Z again.

Somebody at Forza is allowing one part of the program alter another part of the program which means that they aren't clearing the old data being passed along.

So position player in Lego Car z = z -10

Has shifted the camera for a house because they passed that along into all of the code. That's called a bodge... bad programming.

Edited by user Wednesday, July 10, 2019 5:02:38 AM(UTC)  | Reason: Not specified

Notification

Icon
Error