• This is a reminder of 3 IMPORTANT RULES:

    1- External self-promotion websites or apps are NOT allowed here, like Discord/Twitter/Patreon/etc.

    2- Do NOT post in other languages. English-only.

    3- Crack/Warez/Piracy talk is NOT allowed.

    Breaking any of the above rules will result in your messages being deleted and you will be banned upon repetition.

    Please, stop by this thread SoccerGaming Forum Rules And Guidelines and make sure you read and understand our policies.

    Thank you!

Extracting BCData Camera Folder

MonkeyDragon

MonkeyDragon

Senior Squad
bangus;3867293 said:
Cam edits worked last year for all cams. Therefore where the cam is positioned doesn't seem to be the issue, and the problem must be due to something else. Also, it could be the broadcast cam is the only cam with an issue, nobody has even checked that.
Click to expand...

Cam value in .db just an "EA tweak" for each stadiums.

The previous fifa uses just 1 fifacamera.dat & "camera_modifier" to tweak.

While 14,15,16 EA added new thing call "gameplay camera" and "stadium camera" (for cinematics, menu)

The main file now is bcgameplay.dat, all others bcgameplay_x.dat just a customization. You won't see bcgameplay_1.dat (Old Trafford) this year. But no problem, we can MANUALLY add it (then no need edit bcgameplay.dat anymore), hexaediting which camera will be used at Old Trafford.

To sum up, FIFA Next Gen Camera = bcgameplay.dat + (bcgameplay_x.dat) + .db tweak.

The matter of hexaediting camera is not simple. There are many field to edit, it also depends on stadium structure (avoid stand, crowd...)
 
M

mac1975

Club Supporter
MonkeyDragon;3867316 said:
Cam value in .db just an "EA tweak" for each stadiums.

The previous fifa uses just 1 fifacamera.dat & "camera_modifier" to tweak.

While 14,15,16 EA added new thing call "gameplay camera" and "stadium camera" (for cinematics, menu)

The main file now is bcgameplay.dat, all others bcgameplay_x.dat just a customization. You won't see bcgameplay_1.dat (Old Trafford) this year. But no problem, we can MANUALLY add it (then no need edit bcgameplay.dat anymore), hexaediting which camera will be used at Old Trafford.

To sum up, FIFA Next Gen Camera = bcgameplay.dat + (bcgameplay_x.dat) + .db tweak.

The matter of hexaediting camera is not simple. There are many field to edit, it also depends on stadium structure (avoid stand, crowd...)
Click to expand...

That makes sense. What do you think the chances are of being able to make a mod/tool that will enable us to play on the same broadcast camera angle/angle for every stadium which works without being able to see stand etc? Is this achievable?

Cheers
 
B

bangus

Starting XI
mac1975;3867335 said:
play on the same broadcast camera angle/angle for every stadium which works without being able to see stand etc?
Click to expand...
Doesn't that depend on zoom value and where you are trying to position your cam? I used the pro cam, zoomed out 50 yards, 100 yards, all the way out to a blimp view. Not once was the stadium structure in the way, I was able to see the whole pitch and play the game without the stadium structure getting in the way.
 
M

mac1975

Club Supporter
bangus;3867336 said:
Doesn't that depend on zoom value and where you are trying to position your cam? I used the pro cam, zoomed out 50 yards, 100 yards, all the way out to a blimp view. Not once was the stadium structure in the way, I was able to see the whole pitch and play the game without the stadium structure getting in the way.
Click to expand...

I think pro cam must be different than broadcast in that respect. For example, on Wembley I set cam height to 500 and zoom to -100 and it was perfect for me. However, using the same edit with Old Trafford is useless as the stand displays over the near touch line. Some other stadiums are the same - especially when the ball goes into the near corners. In addition, using those parameters on the likes of Stamford Bridge doesn't seem to alter zoom/height at all, but used with the Etihad Stadium the camera is way, way too zoomed out.
 
B

bangus

Starting XI
mac1975;3867342 said:
I think pro cam must be different than broadcast in that respect. For example, on Wembley I set cam height to 500 and zoom to -100 and it was perfect for me. However, using the same edit with Old Trafford is useless as the stand displays over the near touch line. Some other stadiums are the same - especially when the ball goes into the near corners. In addition, using those parameters on the likes of Stamford Bridge doesn't seem to alter zoom/height at all, but used with the Etihad Stadium the camera is way, way too zoomed out.
Click to expand...
Oh okay, so you've checked other cams and such. Yeah I guess I'm just lucky then, I've used the pro cam exclusively since 2008 and nothing else.
 
Fidel Gameplay

Fidel Gameplay

Senior Squad
Hello to everyone, I've discovered an important way to edit all fifa 16 cameras (gameplay, nis, celebration and intros cameras).
Is like a fifa revolution camera mod, all related cameras xml files are stored into:
data/bcdata/muse/musedata-match.big (data_patch.big)

museindex.xml (all files inside this big - not all in this post cause I've reached maximum post characters)
Code: 
<museindex version="1.0">
	<package file="packages\base\base.xml"/>
	<package file="packages\base\intro_base.xml"/>
	<package file="packages\base\subsitution_base.xml"/>
	<package file="packages\champion_nis\package_championNIS_celebrate.xml"/>
	<package file="packages\champion_nis\package_championNIS_celebrate_2.xml"/>
	<package file="packages\champion_nis\package_championNIS_fireworks.xml"/>
	<package file="packages\champion_nis\package_championNIS_minor.xml"/>
	<package file="packages\champion_nis\package_championNIS_podium.xml"/>
	<package file="packages\champion_nis\package_championNIS_team_photo.xml"/>
	<package file="packages\cornerkick\package_cornerkick_deflection_replay.xml"/>
	<package file="packages\cornerkick\package_cornerkick_save_replay.xml"/>
	<package file="packages\cornerkick\package_cornerkick_save_replay_emotion.xml"/>
	<package file="packages\cornerkick\package_cornerkick_unintentional_endplay.xml"/>
	<package file="packages\cornerkick\package_cornerkick_unintentional_endplay_goalkeeper_rush.xml"/>
	<package file="packages\cornerkick\package_gamecam_oop_cornerkick.xml"/>
	<package file="packages\cornerkick\package_move_to_ball.xml"/>
	<package file="packages\cornerkick\package_pickup_ball.xml"/>
	<package file="packages\cornerkick\package_place_ball.xml"/>
	<package file="packages\foul\package_foul_referee_approach_nobooking_skippoint.xml"/>
	<package file="packages\foul\package_foul_referee_approach_pk.xml"/>
	<package file="packages\foul\package_foul_referee_point_penalty.xml"/>
	<package file="packages\foul\package_foul_replay.xml"/>
	<package file="packages\foul\package_foul_replay_no_booking.xml"/>
	<package file="packages\foul\package_foul_vanishing_spray.xml"/>
	<package file="packages\foul\package_foul_vanishing_spray_ball.xml"/>
	<package file="packages\foul\package_foul_warning.xml"/>
	<package file="packages\foul\package_penalty_setup.xml"/>
	<package file="packages\foul\package_penalty_setup_filler.xml"/>
	<package file="packages\foul\package_show_card_conten_red_react.xml"/>
	<package file="packages\foul\package_show_card_conten_yellow_react.xml"/>
	<package file="packages\foul\package_show_card_red_reaction.xml"/>
	<package file="packages\foul\package_show_card_red_replay.xml"/>
	<package file="packages\foul\package_show_card_yellow_reaction.xml"/>
	<package file="packages\foul_delayed\package_foul_delayed_gamecam_oop.xml"/>
	<package file="packages\foul_delayed\package_foul_delayed_referee_approach.xml"/>
	<package file="packages\foul_delayed\package_foul_delayed_replay.xml"/>
	<package file="packages\foul_delayed\package_foul_delayed_replay_no_booking.xml"/>
	<package file="packages\foul_delayed\package_foul_delayed_warning.xml"/>
	<package file="packages\foul_delayed\package_show_delayed_card_red_reaction.xml"/>
	<package file="packages\foul_delayed\package_show_delayed_card_red_replay.xml"/>
	<package file="packages\foul_delayed\package_show_delayed_card_yellow_reaction.xml"/>
	<package file="packages\gameplay\package_gameplay_camera.xml"/>
	<package file="packages\gameplay\package_gameplay_intro_kickoff_camera.xml"/>
	<package file="packages\gameplay\package_gameplay_intro_kickoff_overlay.xml"/>
	<package file="packages\gameplay\package_gameplay_kickoff.xml"/>
	<package file="packages\gameplay\package_gameplay_kickoff_camera.xml"/>
	<package file="packages\gameplay_setpiece\package_setpiece_cornerkick.xml"/>
	<package file="packages\gameplay_setpiece\package_setpiece_freekick.xml"/>
	<package file="packages\gameplay_setpiece\package_setpiece_goalkick.xml"/>
	<package file="packages\gameplay_setpiece\package_setpiece_penaltykick.xml"/>
	<package file="packages\gameplay_setpiece\package_setpiece_shootout.xml"/>
	<package file="packages\goal\package_goal_cameraflash.xml"/>
	<package file="packages\goal\package_goal_gameplay_cam_filler.xml"/>
	<package file="packages\goal\package_goal_golden.xml"/>
	<package file="packages\goal\package_goal_golden_own.xml"/>
	<package file="packages\goal\package_goal_mass_ucc.xml"/>
	<package file="packages\goal\package_goal_mass_ucc_camera.xml"/>
	<package file="packages\goal\package_goal_mass_ucc_camera_pkshootout.xml"/>
	<package file="packages\goal\package_goal_mass_ucc_camera_pkshootout_replay.xml"/>
	<package file="packages\goal\package_goal_mass_ucc_pkshootout.xml"/>
	<package file="packages\goal\package_goal_mass_ucc_pkshootout_replay.xml"/>
	<package file="packages\goal\package_goal_own_goal.xml"/>
	<package file="packages\goal\package_goal_own_goal_replay.xml"/>
	<package file="packages\goal\package_goal_replay.xml"/>
	<package file="packages\goal\package_goal_replay_pkshootout.xml"/>
	<package file="packages\goal\package_goal_skip_point.xml"/>
	<package file="packages\goal\package_goal_ucc.xml"/>
	<package file="packages\goal\package_goal_ucc_for_the_camera.xml"/>
	<package file="packages\goal\package_goal_ucc_shootout.xml"/>
	<package file="packages\goal\package_goal_ucc_special.xml"/>
	<package file="packages\goalkick\package_gk_gamecam_oop.xml"/>
	<package file="packages\goalkick\package_gk_missed_shot_replay.xml"/>
	<package file="packages\goalkick\package_gk_missed_shot_replay_emotion.xml"/>
	<package file="packages\goalkick\package_gk_move_to_ball.xml"/>
	<package file="packages\goalkick\package_gk_pass_ball_to_keeper.xml"/>
	<package file="packages\goalkick\package_gk_place_ball.xml"/>
	<package file="packages\goalkick\package_gk_unintentional_endplay.xml"/>
	<package file="packages\goallinetech\package_corner_goallinetech_nogoal.xml"/>
	<package file="packages\goallinetech\package_fk_goallinetech_nogoal.xml"/>
	<package file="packages\goallinetech\package_gk_goallinetech_nogoal.xml"/>
	<package file="packages\goallinetech\package_goallinetech_goal.xml"/>
	<package file="packages\goallinetech\package_goallinetech_owngoal.xml"/>
	<package file="packages\heat_replays\package_heat_replay.xml"/>
	<package file="packages\heat_replays\package_heat_replay_fk.xml"/>
	<package file="packages\heat_replays\package_heat_replay_sub.xml"/>
	<package file="packages\highlight\package_highlight_block.xml"/>
	<package file="packages\highlight\package_highlight_block_emotion.xml"/>
	<package file="packages\highlight\package_highlight_crowd_chant.xml"/>
	<package file="packages\highlight\package_highlight_foul.xml"/>
	<package file="packages\highlight\package_highlight_foul_emotion.xml"/>
	<package file="packages\highlight\package_highlight_foul_no_card.xml"/>
	<package file="packages\highlight\package_highlight_goal.xml"/>
	<package file="packages\highlight\package_highlight_goal_with_ucc.xml"/>
	<package file="packages\highlight\package_highlight_kickoff.xml"/>
	<package file="packages\highlight\package_highlight_missed_shot.xml"/>
	<package file="packages\highlight
	<package file="packages\intro\subpackage_intro_team_talking_point_early.xml"/>
	<package file="packages\intro\subpackage_intro_team_talking_point_late.xml"/>
	<package file="packages\intro
</museindex>

Now you can imagine how much you can edit in this game about cameras, intros cameras, nis cameras, gameplay cameras.
I've worked and checked out this muse data file on the 15 version also,
when I've tried to edit many aspects of cameras and nis (all).
I've started continuing this work for 16 when I've seen this file included in latest ea official update.
With the methot I'll describe here you can edit the gameplay camera globally, all edits are applied to all user's selected camera.
With this method you can't corrupt the career, because you don't touch the xml file from db.
Anyway monkey dragon method still stable and best.

I'll share the knowledge for everyone want to try to edit or check my actual work and situation about.

Ok, start to edit files in musedata-match.big and enable edits in game, make working edited files inside the muse.
And just if an available programmer from fifa community have free time and inspiration to create a gui tool to easy edit.
If I've created in you the ispiration you can contact me. I'm busy and I've no free time to release it.
Anyway I'll attach to this post my modded muse big, and easy to edit, but without a gui interface.
For the fifa community this muse file is really unfamiliar, but beleave me you can do amazing edits.
For example you can add new features an a default camera or intro.
For example you can use the final champions intro on the friendly match, you can fix the podium camera (wrong zoom on the default game).
You can add, remove, and tweak all cameras and cinematics cameras present into the game.
For example you can see the player go to ball for the corner kick, on default you can see the large camera and player going, ok,
by modifying some codes on the related xml file for example is possible to switch the camera see the player in his face like a frontal sideline sky camera.
I'm currently study the whole structure but is like a 16 revolution camera mod, and for a lot of cameras or special cameras are connected to players overalls, etc.

Ok let's see what happens.

Info, tips and history about

Step 1:
extract and decompress the musedata-match.big from the big file, regenerate data_patch.bh, ok (no problem, common method).
Now the game read the musedata-match.big from folder.

Step 2:
The problem (not easy to solve but now solved, you can see pics below with edits working):
how to make working files edited inside the musedata-match.big?
how to regenerate if the bh file isn't present?
Ok bypass for now these problems, I'll solve after checking out xml files inside the muse, here some details:
packages\gameplay\package_gameplay_camera.xml (boom!) global fifa gameplay camera settings
below an little extract of the code in the file, the important <CameraInstance> section,

original default code:
Code: 
<CameraCollection>
          <CameraInstance>
            <property name="cameraName" type="string" value="UserGameplayCamera" />
            <property name="cameraBehavior" type="string" value="gameplaybehavior" />
            <property name="cameraEvaluators" type="int" value="0" />
            <property name="leadingEnabled" type="bool" value="True" />
            <property name="cameraFramingOption" type="int" value="0" />
            <property name="blendLength" type="float" value="5" />
            <property name="blendCurve" type="int" value="4" />
            <property name="blendPolicy" type="int" value="1" />
            <ZoomModifierCollection />
            <FocalDistModifierCollection />
          </CameraInstance>
        </CameraCollection>

new tweak modded code (zoom modifier addon - the red code):
Code: 
<CameraCollection>
          <CameraInstance>
            <property name="cameraName" type="string" value="UserGameplayCamera" />
            <property name="cameraBehavior" type="string" value="gameplaybehavior" />
            <property name="cameraEvaluators" type="int" value="0" />
            <property name="leadingEnabled" type="bool" value="True" />
            <property name="cameraFramingOption" type="int" value="0" />
            <property name="blendLength" type="float" value="10" />
            <property name="blendCurve" type="int" value="4" />
            <property name="blendPolicy" type="int" value="1" />
            [COLOR="Red"]<property name="zoomInitialValue" type="float" value="0.60" />
            <ZoomModifierCollection>
              <ZoomModifier>
                <property name="zoomFinalValue" type="float" value="0.60" />
              </ZoomModifier>[/COLOR]
            </ZoomModifierCollection>
            <FocalDistModifierCollection />
          </CameraInstance>
        </CameraCollection>

In these next days I'll send other tips, about other files for:
<package file="packages\gameplay_setpiece\package_setpiece_cornerkick.xml"/>
<package file="packages\gameplay_setpiece\package_setpiece_freekick.xml"/>
<package file="packages\gameplay_setpiece\package_setpiece_goalkick.xml"/>

or about:
<package file="packages\gameplay\package_gameplay_intro_kickoff_camera.xml
kick off means ball on the center and start match, you can see the variable zoom
(is possible to edit zoom values and transition time, is possible to edit all off these settings for all game cameras, celebrations, stadium intro, etc.)
(edited and included in the pack - because you must readapt the variable zoom to new camera, anyway the effect is amazing now).

You can extract all xml files with FM or CG File Explorer.

Step 4
Import edited file into the muse:
I've used and hex editor and I've imported new edited xml file into the muse big like a block (BIG4 format),
is important that you must import the new xml file in the same block of default file into the big.
Anyway you can try fifafs from cmd. In the fact you must import uncompressed files into the muse big and game read and no crash.
Another good news, now new uncompressed modded files are available to edit with FinalBIG.
In the fact at moment now you can download my camera mod pack, you can open my special muse big with FinalBIG,
browse and select:
packages\gameplay\package_gameplay_camera.xml (you can see the content of my uncompressed xml files in the final big editor)
go in
Code: 
<property name="zoomInitialValue" type="float" value="0.60" />
            <ZoomModifierCollection>
              <ZoomModifier>
                <property name="zoomFinalValue" type="float" value="0.60" />

edit my 0.60 zoom values as you want -- use same values for min (Initial) and max (Final), I'll explain in the future other tips.
working range is from 0.50 (view from far away, no more lowered than 0.5, game loose allumination) to 4.0 (nearly on the pitch with manager),
anyway you can test out your favorire setup and try out effect in-gameplay.
On the sections you can also edit the cameraEvaluators value to switch to other cameras in the precise moment,
I'll share a list of value asap (but you can try 0, 10, 46 but I think the range is from 0 default for all user cameras and to 46 and othe values for specifics)
On my camera I've also increased blendLength from 5 (default) to 10, anyway you can test your favorite.
Save big file and enjoy!

There are also other files available to edit in my camera pack mod.
You can test your favorite user camera setting to adjust the zoom.


For example with 0.60 value I'see the gameplay camera like pics below, really amazing for online games, you can see all the pitch, and free spaces.
By installing this camera mod with this incredible tweak you can see another game, especially online, but also on offline matches versus the cpu.
Now you truly have a complete view of the playing field.
Many mod pics here (on the version included in this post the gk kick cameras is the default and not like the one included in these pics:








At moment you can download this first beta version of the 16 rev camera mod from here:
http://1drv.ms/1Ynj4pX
(included user gameplay camera mod and addons cameras tweaks, that you can see in the game)

INSTALLATION
copy my data folder in your 16 folder and regenerate. Start game enjoy!
I suggest 0.60 for online games, and 0.85 or 1.0 for career games.
Anyway is possible that I'll release an easy tool to switch pre-customizated camera values.
But I thinks the best way is that the user can edit through a gui editor all camera's setting and customize at his pleasure.
Remember that at moment you can edit only the files I've imported with my method, original files are compressed.
I'll share the whole muse editable on this next days, with this special muse you can easy edit the xml file directly into the muse with finalbig.
On the big included there are many duplicated files, it was done on purpose.
On this version I've also edited some stadium's exterior zoom.
Let me know if you like!
 
M

mac1975

Club Supporter
Wow Fidel, this looks fantastic. Am I correct in thinking that I would be able to set the same zoom/height on broadcast cameras globally? So every stadium has the same same angle, height and zoom on broadcast without editing parameters for each stadium?

Cheers
 
S

s33k3rgr

Club Supporter
Fidel bravo for your findings. Some of us though find those gibberish (fifa editing noobs) and would like a simple tutorial from start to end . Thanks anyways i am sure tutorial will come soon (and which tools we need).
 
B

bjama

Youth Team
Leonardo Da vinci
Galileo Galilei
Guglielmo marconi
Fidel

italian do it better


ps: now every camera is awesome: dynamic is fantastic decrease zoom:-)
 
B

bangus

Starting XI
s33k3rgr;3867559 said:
Fidel bravo for your findings. Some of us though find those gibberish (fifa editing noobs) and would like a simple tutorial from start to end . Thanks anyways i am sure tutorial will come soon (and which tools we need).
Click to expand...
I provided you with a detailed description of how to edit the meta file, how to create a db file, and I even posted download links for you. As for your "wait for the tools we need" comment, Fidel has already provided a clearly-written tutorial that people here are successfully using to edit the cams. Sounds to me this is less about not knowing how to edit, and more about not interested in learning how. BTW, when someone goes out of their way to answer your questions and help you (several times), it's customary to thank them.
 
M

mac1975

Club Supporter
s33k3rgr;3867559 said:
Fidel bravo for your findings. Some of us though find those gibberish (fifa editing noobs) and would like a simple tutorial from start to end . Thanks anyways i am sure tutorial will come soon (and which tools we need).
Click to expand...

All you need to do is download Fidel's file then copy the content of the FIFA 16 folder (which is fifa16/data/bcdata) to your FIFA 16 folder then regenerate. I use i68 controller to regenerate as it is really straightforward.

It all works perfectly Fidel, fantastic work. I was wondering if it was possible to edit camera height? I've had a play around with it but not manage to yet. The possibilities for the other cameras are fantastic though!

Cheers
 
You must log in or register to reply here.


Top