-
Please see the most recent updates in the "Where did the .com name go?" thread. Posts number 16 and 17.
shared.dds
- Thread starter mongoose
- Start date
BorekS
Members +
as Mixxer says, same named .dds files causing not any such warning messages, just visual issues.
the most close reason of the message seems is really a 3d object duplicty. it also can be defined twice or more in some .xdp and/or .cfg file.
for such kind of "research" I would reccommend to use some decent file manager, which can search the files including inside (means the current file content), for example the Total Commander.
the most close reason of the message seems is really a 3d object duplicty. it also can be defined twice or more in some .xdp and/or .cfg file.
for such kind of "research" I would reccommend to use some decent file manager, which can search the files including inside (means the current file content), for example the Total Commander.
MajorMagee
SOH-CM-2022
I just use the Windows Search function in the Aircraft directory. I would start with looking for the word shared and see what turns up.
The other possibility is that you have more than one Aircraft.cfg file with an entry of model = shared. This would be more difficult to track down, but starting with your most recent aircraft additions should help.
The other possibility is that you have more than one Aircraft.cfg file with an entry of model = shared. This would be more difficult to track down, but starting with your most recent aircraft additions should help.
mongoose
SOH-CM-2026
You can be sure I have done is search in ALL folders; not only this install but others!
Now there are plenty of dds files with 'shared' as part of the name but none just 'shared.dds'. Even then I only found one duplication and removing them did not solve the issue. My ? was; did anyone actually have a 'shared.dds' anywhere?
Now there are plenty of dds files with 'shared' as part of the name but none just 'shared.dds'. Even then I only found one duplication and removing them did not solve the issue. My ? was; did anyone actually have a 'shared.dds' anywhere?
BorekS
Members +
the message is about unitdata model, I cant see there any patterns of dds texture file 
as Mixxer and Major already wrote, the point is a duplication of a model (name), you have to check the m3d filenames and mainly the content of airplane cfg and xdp files.
with the tool Ive mentioned its a matter of milliseconds to discover the issue.
as Mixxer and Major already wrote, the point is a duplication of a model (name), you have to check the m3d filenames and mainly the content of airplane cfg and xdp files.
with the tool Ive mentioned its a matter of milliseconds to discover the issue.
I also suspect some WOTR buildings or vehicles I added.
mongoose
SOH-CM-2026
Well that is odd! I established it was some WOTR vehicle I had added by simply replacing the whole folder with my back up one (always have one!
) Then I searched for the word 'shared' in the folder of the WOTR vehicles I needed for gsl facilities and came across a folder called "shared" with one crate.dds file in it. I placed that dds outside the folder and deleted the folder. That seemed to do the trick; for now anyway!
) Then I searched for the word 'shared' in the folder of the WOTR vehicles I needed for gsl facilities and came across a folder called "shared" with one crate.dds file in it. I placed that dds outside the folder and deleted the folder. That seemed to do the trick; for now anyway!
BorekS
Members +
good youve solved it, mate
as to the other possible issue causing:
current airplane CFG file, always called aircraft.cfg contents a section called [fltsim.*] where is defined what for model will use current flight model, eg:
sim=Ju_88 //means Ju_88.AIR
model=ju_88a_4 //ju_88a_4.M3D
current airplane XDP file contents a section called <UnitData> where is defined which m3d ariplne model is used, see for ModelName there, eg. in ju_88a_4.xdp you will find ModelName="ju_88a_4.m3d".
if somewhere in the game file content is such kind of naming duplicity, you can easy get problems
as to the other possible issue causing:
current airplane CFG file, always called aircraft.cfg contents a section called [fltsim.*] where is defined what for model will use current flight model, eg:
sim=Ju_88 //means Ju_88.AIR
model=ju_88a_4 //ju_88a_4.M3D
current airplane XDP file contents a section called <UnitData> where is defined which m3d ariplne model is used, see for ModelName there, eg. in ju_88a_4.xdp you will find ModelName="ju_88a_4.m3d".
if somewhere in the game file content is such kind of naming duplicity, you can easy get problems