Djey

Announcement : TDUF toolset 0.4.1 (hotfix) now available !
 
 
* Research+FileTool(applyJson): fixes a bug causing incorrect data written from json file
* Research: applies latest updates to BIN-cameras file structure.
 
 
 
See first post to download!

Updated structure for cameras.bin files !
http://bit.ly/1GARTAJ

Updated structure for cameras.bin files !
http://bit.ly/1GARTAJ

Updated structure for cameras.bin files !
http://bit.ly/1GARTAJ

great one star,thanks, i put 300sl camera ,it fits great,...wow,never though i see combat,..zoqqer,..and star agreed on something ....the world is about to collapse ...lol...

Closed thread: you'll find updated documentation within TDUCP project:

https://github.com/djey47/tdu-cp/wiki/TDUF-Customizing-Cameras

 
Cameras overbloating attempts
 
Hi everyone,
today, we'll try to use TDUF tools to make something good :evil:
 
Now it is known that a lot of camera sets are missing to handle bunch of new cars which will be added as totally new slots.
Thus, I've modified cameras.bin file the following way: duplicating an existing camera entry (#108) to a new one (#10108).
 
For your information, this camera is the one used by the ASTON MARTIN DB7 Zagato.
 
Are there people willing to try it :
- it should not brake existing TDU configuration
- this new camera id (10108) is meant to be freely assigned to an existing vehicle (CarPhysics_Data).
 

 
To apply, unzip and copy file below into Test Drive/Euro/Bnk/Database directory. Please backup existing cameras.bin file before trying anything!
 
 
If it works, it might be possible to duplicate all existing cameras - my goal is having clones of existing at id + 10000.
 
Thanks !
 
Edit: Previous attachment was causing TDU to crash. Hope it's fixed now. Please redownload - sorry for incovenience.
 
---
 
Note about second attachment:
This brand new file contains 149 camera sets more, which are clones of genuine cameras sets. And can be customized without affecting source sets.
 
Feel free to test with your game.
 
With car physics, simply add 10000 to original camera set id to use the new one :)
e.g To use clone of camera set #108 (DB7 Zagato), use set #10108.
 
Btw, here is a readable, json file from this new Cameras.bin: http://bit.ly/1APLhaK
 
Enjoy! :evil:
 
TUTORIALS
Below, a guide how to use TDUF CameraTool (available in version 0.5+).
 
Prerequisites
TDUF toolset must be installed and working normally. See TDUF thread and README in zip archive for details.
 
A. Duplicate a single camera set
Available from TDUF 0.5.
Given its #id, you can create a brand new camera set from it.
 
Syntax: CameraTool copy-all-sets -i "cameras.bin" -o "new cameras.bin" -s sourceCameraIdentifier -t newCameraIndentifier
 
 
 
 
B. Duplicate all genuine camera sets
Available from TDUF 0.5.
These are all camera sets ranging from #1 to #10000. TDU with Megapack gets 149 camera sets.
 
Syntax: CameraTool copy-all-sets -i "cameras.bin" -o "new cameras.bin" -t baseOfNewCameraIdentifiers
 
 
 
 
C. Re-use a view from a set to another
Available from TDUF 0.8.
Given #id of source and target cameras + view type, you will be able to replace view in target camera by the one in source.
 
D. Customize view settings
 
Feature not planned yet

Closed thread: you'll find updated documentation within TDUCP project:

https://github.com/djey47/tdu-cp/wiki/TDUF-Customizing-Cameras

 
Cameras overbloating attempts
 
Hi everyone,
today, we'll try to use TDUF tools to make something good :evil:
 
Now it is known that a lot of camera sets are missing to handle bunch of new cars which will be added as totally new slots.
Thus, I've modified cameras.bin file the following way: duplicating an existing camera entry (#108) to a new one (#10108).
 
For your information, this camera is the one used by the ASTON MARTIN DB7 Zagato.
 
Are there people willing to try it :
- it should not brake existing TDU configuration
- this new camera id (10108) is meant to be freely assigned to an existing vehicle (CarPhysics_Data).
 

 
To apply, unzip and copy file below into Test Drive/Euro/Bnk/Database directory. Please backup existing cameras.bin file before trying anything!
 
 
If it works, it might be possible to duplicate all existing cameras - my goal is having clones of existing at id + 10000.
 
Thanks !
 
Edit: Previous attachment was causing TDU to crash. Hope it's fixed now. Please redownload - sorry for incovenience.
 
---
 
Note about second attachment:
This brand new file contains 149 camera sets more, which are clones of genuine cameras sets. And can be customized without affecting source sets.
 
Feel free to test with your game.
 
With car physics, simply add 10000 to original camera set id to use the new one :)
e.g To use clone of camera set #108 (DB7 Zagato), use set #10108.
 
Btw, here is a readable, json file from this new Cameras.bin: http://bit.ly/1APLhaK
 
Enjoy! :evil:
 
TUTORIALS
Below, a guide how to use TDUF CameraTool (available in version 0.5+).
 
Prerequisites
TDUF toolset must be installed and working normally. See TDUF thread and README in zip archive for details.
 
A. Duplicate a single camera set
Available from TDUF 0.5.
Given its #id, you can create a brand new camera set from it.
 
Syntax: CameraTool copy-all-sets -i "cameras.bin" -o "new cameras.bin" -s sourceCameraIdentifier -t newCameraIndentifier
 
 
 
 
B. Duplicate all genuine camera sets
Available from TDUF 0.5.
These are all camera sets ranging from #1 to #10000. TDU with Megapack gets 149 camera sets.
 
Syntax: CameraTool copy-all-sets -i "cameras.bin" -o "new cameras.bin" -t baseOfNewCameraIdentifiers
 
 
 
 
C. Re-use a view from a set to another
Available from TDUF 0.8.
Given #id of source and target cameras + view type, you will be able to replace view in target camera by the one in source.
 
D. Customize view settings
 
Feature not planned yet

Closed thread: you'll find updated documentation within TDUCP project:

https://github.com/djey47/tdu-cp/wiki/TDUF-Customizing-Cameras

 
Cameras overbloating attempts
 
Hi everyone,
today, we'll try to use TDUF tools to make something good :evil:
 
Now it is known that a lot of camera sets are missing to handle bunch of new cars which will be added as totally new slots.
Thus, I've modified cameras.bin file the following way: duplicating an existing camera entry (#108) to a new one (#10108).
 
For your information, this camera is the one used by the ASTON MARTIN DB7 Zagato.
 
Are there people willing to try it :
- it should not brake existing TDU configuration
- this new camera id (10108) is meant to be freely assigned to an existing vehicle (CarPhysics_Data).
 

 
To apply, unzip and copy file below into Test Drive/Euro/Bnk/Database directory. Please backup existing cameras.bin file before trying anything!
 
 
If it works, it might be possible to duplicate all existing cameras - my goal is having clones of existing at id + 10000.
 
Thanks !
 
Edit: Previous attachment was causing TDU to crash. Hope it's fixed now. Please redownload - sorry for incovenience.
 
---
 
Note about second attachment:
This brand new file contains 149 camera sets more, which are clones of genuine cameras sets. And can be customized without affecting source sets.
 
Feel free to test with your game.
 
With car physics, simply add 10000 to original camera set id to use the new one :)
e.g To use clone of camera set #108 (DB7 Zagato), use set #10108.
 
Btw, here is a readable, json file from this new Cameras.bin: http://bit.ly/1APLhaK
 
Enjoy! :evil:
 
TUTORIALS
Below, a guide how to use TDUF CameraTool (available in version 0.5+).
 
Prerequisites
TDUF toolset must be installed and working normally. See TDUF thread and README in zip archive for details.
 
A. Duplicate a single camera set
Available from TDUF 0.5.
Given its #id, you can create a brand new camera set from it.
 
Syntax: CameraTool copy-all-sets -i "cameras.bin" -o "new cameras.bin" -s sourceCameraIdentifier -t newCameraIndentifier
 
 
 
 
B. Duplicate all genuine camera sets
Available from TDUF 0.5.
These are all camera sets ranging from #1 to #10000. TDU with Megapack gets 149 camera sets.
 
Syntax: CameraTool copy-all-sets -i "cameras.bin" -o "new cameras.bin" -t baseOfNewCameraIdentifiers
 
 
 
 
C. Re-use a view from a set to another
Available from TDUF 0.8.
Given #id of source and target cameras + view type, you will be able to replace view in target camera by the one in source.
 
D. Customize view settings
 
Feature not planned yet

Closed thread: you'll find updated documentation within TDUCP project:

https://github.com/djey47/tdu-cp/wiki/TDUF-Customizing-Cameras

 
Cameras overbloating attempts
 
Hi everyone,
today, we'll try to use TDUF tools to make something good :evil:
 
Now it is known that a lot of camera sets are missing to handle bunch of new cars which will be added as totally new slots.
Thus, I've modified cameras.bin file the following way: duplicating an existing camera entry (#108) to a new one (#10108).
 
For your information, this camera is the one used by the ASTON MARTIN DB7 Zagato.
 
Are there people willing to try it :
- it should not brake existing TDU configuration
- this new camera id (10108) is meant to be freely assigned to an existing vehicle (CarPhysics_Data).
 

 
To apply, unzip and copy file below into Test Drive/Euro/Bnk/Database directory. Please backup existing cameras.bin file before trying anything!
 
 
If it works, it might be possible to duplicate all existing cameras - my goal is having clones of existing at id + 10000.
 
Thanks !
 
Edit: Previous attachment was causing TDU to crash. Hope it's fixed now. Please redownload - sorry for incovenience.
 
---
 
Note about second attachment:
This brand new file contains 149 camera sets more, which are clones of genuine cameras sets. And can be customized without affecting source sets.
 
Feel free to test with your game.
 
With car physics, simply add 10000 to original camera set id to use the new one :)
e.g To use clone of camera set #108 (DB7 Zagato), use set #10108.
 
Btw, here is a readable, json file from this new Cameras.bin: http://bit.ly/1APLhaK
 
Enjoy! :evil:
 
TUTORIALS
Below, a guide how to use TDUF CameraTool (available in version 0.5+).
 
Prerequisites
TDUF toolset must be installed and working normally. See TDUF thread and README in zip archive for details.
 
A. Duplicate a single camera set
Available from TDUF 0.5.
Given its #id, you can create a brand new camera set from it.
 
Syntax: CameraTool copy-all-sets -i "cameras.bin" -o "new cameras.bin" -s sourceCameraIdentifier -t newCameraIndentifier
 
 
 
 
B. Duplicate all genuine camera sets
Available from TDUF 0.5.
These are all camera sets ranging from #1 to #10000. TDU with Megapack gets 149 camera sets.
 
Syntax: CameraTool copy-all-sets -i "cameras.bin" -o "new cameras.bin" -t baseOfNewCameraIdentifiers
 
 
 
 
C. Re-use a view from a set to another
Available from TDUF 0.8.
Given #id of source and target cameras + view type, you will be able to replace view in target camera by the one in source.
 
D. Customize view settings
 
Feature not planned yet

Closed thread: you'll find updated documentation within TDUCP project:

https://github.com/djey47/tdu-cp/wiki/TDUF-Customizing-Cameras

 
Cameras overbloating attempts
 
Hi everyone,
today, we'll try to use TDUF tools to make something good :evil:
 
Now it is known that a lot of camera sets are missing to handle bunch of new cars which will be added as totally new slots.
Thus, I've modified cameras.bin file the following way: duplicating an existing camera entry (#108) to a new one (#10108).
 
For your information, this camera is the one used by the ASTON MARTIN DB7 Zagato.
 
Are there people willing to try it :
- it should not brake existing TDU configuration
- this new camera id (10108) is meant to be freely assigned to an existing vehicle (CarPhysics_Data).
 

 
To apply, unzip and copy file below into Test Drive/Euro/Bnk/Database directory. Please backup existing cameras.bin file before trying anything!
 
 
If it works, it might be possible to duplicate all existing cameras - my goal is having clones of existing at id + 10000.
 
Thanks !
 
Edit: Previous attachment was causing TDU to crash. Hope it's fixed now. Please redownload - sorry for incovenience.
 
---
 
Note about second attachment:
This brand new file contains 149 camera sets more, which are clones of genuine cameras sets. And can be customized without affecting source sets.
 
Feel free to test with your game.
 
With car physics, simply add 10000 to original camera set id to use the new one :)
e.g To use clone of camera set #108 (DB7 Zagato), use set #10108.
 
Btw, here is a readable, json file from this new Cameras.bin: http://bit.ly/1APLhaK
 
Enjoy! :evil:
 
TUTORIALS
Below, a guide how to use TDUF CameraTool (available in version 0.5+).
 
Prerequisites
TDUF toolset must be installed and working normally. See TDUF thread and README in zip archive for details.
 
A. Duplicate a single camera set
Available from TDUF 0.5.
Given its #id, you can create a brand new camera set from it.
 
Syntax: CameraTool copy-all-sets -i "cameras.bin" -o "new cameras.bin" -s sourceCameraIdentifier -t newCameraIndentifier
 
 
 
 
B. Duplicate all genuine camera sets
Available from TDUF 0.5.
These are all camera sets ranging from #1 to #10000. TDU with Megapack gets 149 camera sets.
 
Syntax: CameraTool copy-all-sets -i "cameras.bin" -o "new cameras.bin" -t baseOfNewCameraIdentifiers
 
 
 
 
C. Re-use a view from a set to another
Available from TDUF 0.8.
Given #id of source and target cameras + view type, you will be able to replace view in target camera by the one in source.
 
D. Customize view settings
 
Feature not planned yet

It's time to add cam slots then. 
Cameras.bin format support has been improved in latest TDUF release.
So maybe great time to try adding new ones ? Shall we need a dedicated research thread for that ?

It's time to add cam slots then. 
Cameras.bin format support has been improved in latest TDUF release.
So maybe great time to try adding new ones ? Shall we need a dedicated research thread for that ?

Yes, ensuring compatibility is important, that's why I will try not to make braking changes while staying at same major version (is currently 0.x)
 
So all users/devs can always enjoy new features and bugfixes, and previous features at the same time :)

Yes, ensuring compatibility is important, that's why I will try not to make braking changes while staying at same major version (is currently 0.x)
 
So all users/devs can always enjoy new features and bugfixes, and previous features at the same time :)

Database fix is a very good idea :) I'm gonna use it for sure in my project. I don't want to see a car having some issues :D
Thanks a lot Djey ! :cool:

Announcement : TDUF toolset 0.4.0 now available !
 
So, what's new ?
* General (cli): new command available in CLI: Version.cmd, displaying current toolset version
* General (cli): commands and examples now sorted by alphabetical order
 
* DatabaseTool (fix): new operation to fix database errors
* DatabaseTool (fix): supports both encrypted and unencrypted DB files (use of -c/--clear parameters)
* DatabaseTool (check): displays details of error 'unconsistent resource count over locales', sorted by alphabetical order
 
* FileTool (toJson/applyJson): processes fully compliant JSON files, respecting file structure
* FileTool (toJson/applyJson): writes and reads byte arrays 'the hex way', e.g 0x[00 A5 BF]
 
* Research: updates cameras.bin structure with known fields
* Research: adds default support for 2DB/2DM/DDS/XMB
 
* Library: misc improvements and bug fixes
* Library: adds support for TDUMT libs as temporary solution for BNK management, embedded in current package.
 
See first post to download!
 
 
IMPORTANT:
unlike stated in README files, feature below has been postponed and will be available in next (0.5.0) release. Sorry.
* FileTool (bankInfo/unpack/repack): new operations to handle TDU Banks files (*.bnk) - experimental feature!

Announcement : TDUF toolset 0.4.0 now available !
 
So, what's new ?
* General (cli): new command available in CLI: Version.cmd, displaying current toolset version
* General (cli): commands and examples now sorted by alphabetical order
 
* DatabaseTool (fix): new operation to fix database errors
* DatabaseTool (fix): supports both encrypted and unencrypted DB files (use of -c/--clear parameters)
* DatabaseTool (check): displays details of error 'unconsistent resource count over locales', sorted by alphabetical order
 
* FileTool (toJson/applyJson): processes fully compliant JSON files, respecting file structure
* FileTool (toJson/applyJson): writes and reads byte arrays 'the hex way', e.g 0x[00 A5 BF]
 
* Research: updates cameras.bin structure with known fields
* Research: adds default support for 2DB/2DM/DDS/XMB
 
* Library: misc improvements and bug fixes
* Library: adds support for TDUMT libs as temporary solution for BNK management, embedded in current package.
 
See first post to download!
 
 
IMPORTANT:
unlike stated in README files, feature below has been postponed and will be available in next (0.5.0) release. Sorry.
* FileTool (bankInfo/unpack/repack): new operations to handle TDU Banks files (*.bnk) - experimental feature!

Announcement : TDUF toolset 0.4.0 now available !
 
So, what's new ?
* General (cli): new command available in CLI: Version.cmd, displaying current toolset version
* General (cli): commands and examples now sorted by alphabetical order
 
* DatabaseTool (fix): new operation to fix database errors
* DatabaseTool (fix): supports both encrypted and unencrypted DB files (use of -c/--clear parameters)
* DatabaseTool (check): displays details of error 'unconsistent resource count over locales', sorted by alphabetical order
 
* FileTool (toJson/applyJson): processes fully compliant JSON files, respecting file structure
* FileTool (toJson/applyJson): writes and reads byte arrays 'the hex way', e.g 0x[00 A5 BF]
 
* Research: updates cameras.bin structure with known fields
* Research: adds default support for 2DB/2DM/DDS/XMB
 
* Library: misc improvements and bug fixes
* Library: adds support for TDUMT libs as temporary solution for BNK management, embedded in current package.
 
See first post to download!
 
 
IMPORTANT:
unlike stated in README files, feature below has been postponed and will be available in next (0.5.0) release. Sorry.
* FileTool (bankInfo/unpack/repack): new operations to handle TDU Banks files (*.bnk) - experimental feature!

Announcement : TDUF toolset 0.4.0 now available !
 
So, what's new ?
* General (cli): new command available in CLI: Version.cmd, displaying current toolset version
* General (cli): commands and examples now sorted by alphabetical order
 
* DatabaseTool (fix): new operation to fix database errors
* DatabaseTool (fix): supports both encrypted and unencrypted DB files (use of -c/--clear parameters)
* DatabaseTool (check): displays details of error 'unconsistent resource count over locales', sorted by alphabetical order
 
* FileTool (toJson/applyJson): processes fully compliant JSON files, respecting file structure
* FileTool (toJson/applyJson): writes and reads byte arrays 'the hex way', e.g 0x[00 A5 BF]
 
* Research: updates cameras.bin structure with known fields
* Research: adds default support for 2DB/2DM/DDS/XMB
 
* Library: misc improvements and bug fixes
* Library: adds support for TDUMT libs as temporary solution for BNK management, embedded in current package.
 
See first post to download!
 
 
IMPORTANT:
unlike stated in README files, feature below has been postponed and will be available in next (0.5.0) release. Sorry.
* FileTool (bankInfo/unpack/repack): new operations to handle TDU Banks files (*.bnk) - experimental feature!

Announcement : TDUF toolset 0.4.0 now available !
 
So, what's new ?
* General (cli): new command available in CLI: Version.cmd, displaying current toolset version
* General (cli): commands and examples now sorted by alphabetical order
 
* DatabaseTool (fix): new operation to fix database errors
* DatabaseTool (fix): supports both encrypted and unencrypted DB files (use of -c/--clear parameters)
* DatabaseTool (check): displays details of error 'unconsistent resource count over locales', sorted by alphabetical order
 
* FileTool (toJson/applyJson): processes fully compliant JSON files, respecting file structure
* FileTool (toJson/applyJson): writes and reads byte arrays 'the hex way', e.g 0x[00 A5 BF]
 
* Research: updates cameras.bin structure with known fields
* Research: adds default support for 2DB/2DM/DDS/XMB
 
* Library: misc improvements and bug fixes
* Library: adds support for TDUMT libs as temporary solution for BNK management, embedded in current package.
 
See first post to download!
 
 
IMPORTANT:
unlike stated in README files, feature below has been postponed and will be available in next (0.5.0) release. Sorry.
* FileTool (bankInfo/unpack/repack): new operations to handle TDU Banks files (*.bnk) - experimental feature!

I agree to duplicate slots as well. Now we can, thus we should make use of it :)
 
Keeping original slots untouched will allow backwards compatibility with previous autoinstallers and people who don't install mods..
The way of installing mod is a matter of taste - I know some don't like autoinstallers, but there are things we can't just set up manually without proper knowledge or via a hard task.
 
Till new hybrid installer ever comes (with more control for advanced users), let's give a choice to gamers ;)

I agree to duplicate slots as well. Now we can, thus we should make use of it :)
 
Keeping original slots untouched will allow backwards compatibility with previous autoinstallers and people who don't install mods..
The way of installing mod is a matter of taste - I know some don't like autoinstallers, but there are things we can't just set up manually without proper knowledge or via a hard task.
 
Till new hybrid installer ever comes (with more control for advanced users), let's give a choice to gamers ;)

I agree to duplicate slots as well. Now we can, thus we should make use of it :)
 
Keeping original slots untouched will allow backwards compatibility with previous autoinstallers and people who don't install mods..
The way of installing mod is a matter of taste - I know some don't like autoinstallers, but there are things we can't just set up manually without proper knowledge or via a hard task.
 
Till new hybrid installer ever comes (with more control for advanced users), let's give a choice to gamers ;)

lmao darky, naaa im not going that fast,
i still got some work to do like updating some of my other old mods aswell
Sry but i dont drink pepsi id rather have a nice and cold beer ;P

No worries, I was just curious ;)