Jump to content

CDDS compatibility with 1.1


Recommended Posts

Guest ThomasDWeiss
Posted

LOMAN 2.1 uses CDDS compression that is NO LONGER fully compatible with 1.1 - does ED have a solution for this problem?

Posted
LOMAN 2.1 uses CDDS compression that is NO LONGER fully compatible with 1.1 - does ED have a solution for this problem?

 

How is it no longer fully compatible with 1.1? - the nature of the CDDS containers has not changed.

 

Anyway, wouldnt it be better to ask the author of the Loman utility about this?

 

- JJ.

JJ

Guest ruggbutt
Posted

Has anyone heard from Skypat?

Posted
Has anyone heard from Skypat?

 

Well last I heard he had moved on to other things, so I dont know...

 

- JJ.

JJ

Guest ThomasDWeiss
Posted

This is far from a trivial question.

 

Ninety nine percent of add-ons are installed with LOMAN, fully 35% do not work if you enable CDDS compression, if it is a cockpit add-on, it will not only NOT work, but you cannot un-install it. Lock On is no longer playable.

 

Also, the F-15 had its structure modified, so many F-15 add-ons cannot be installed with the CDDS option enabled, making them almost useless.

 

I believe it is in the interest of ED to look into this problem, as it affects the work of many of those that created add-ons for Lock On.

Posted

They can use the LockOn Texture Tool (LoTextureTool2.0) instead of the CDDS browser of LoMan2.1 to edit different files in 1.1.

 

Download here:

http://www.checksix-fr.com

 

Regards

Best Regards

Viper

sigpic3353_7.gif

System: Intel Core i7-4790, 3,6GHz, 16GB RAM, 128GB SSD, 2TB HDD, NVIDIA GeForce GTX 960 2GB GDDR5,

TM HOTAS Warthog;(MSFFB2 for testing); TrackIR4 +Track Clip Pro; Windows 10 Pro.

Posted

The problem is that LoMan can handle only DXT5 type of DDS files while LOMAC also uses DXT2 type.

Till 1.02 there were small number of DXT2 textures. But there are many in 1.1.

The ideal solution is to modify LoMan so that it could handle DXT2 files properly.

 

LoMan has the other problems of poor qualities on generation of MipMaps and DDS compression.

I hope these will be solved in a future version of LoMan.

TekaTeka from Japan

[sIGPIC][/sIGPIC]

Visit my site Beyond Visual Range.

Guest ThomasDWeiss
Posted

Maybe it is simply a question of replacing the CDDS browser in Loman by another ?

Posted
Well last I heard he had moved on to other things, so I dont know...

 

- JJ.

 

I heard the same thing Alfa. Maybe you can give us, none loman users a crash course on how to implement mods without loman. If you have the time of course. Would be appreciated. By me thats for sure. The mig skin on the main website. How to implement it without loman? is this possible?

 

Much appreciated

Cheers.

Posted
Maybe it is simply a question of replacing the CDDS browser in Loman by another ?

Maybe.

 

There is another problem in LoMan yet.

LoMan automaically searches a CDDS file that holds a texture to replace.

But there are textures of identical names in different CDDS files now in 1.1 and LoMan can not distinguish them at all. So the textures can be put in the wrong places now.

 

Sigh... :icon_frow

TekaTeka from Japan

[sIGPIC][/sIGPIC]

Visit my site Beyond Visual Range.

Posted
I heard the same thing Alfa. Maybe you can give us, none loman users a crash course on how to implement mods without loman. If you have the time of course. Would be appreciated. By me thats for sure. The mig skin on the main website. How to implement it without loman? is this possible?

 

Much appreciated

Cheers.

 

Well I dont use Loman myself, because I like to know exactly where things go when I install them and because Loman has a nasty tendency not to like it if you swap individual files without using it(which I do all the time when making mods).

 

For installation of textures into the .CDDS containers, you can use a seperate tool called "LoTexture Tool"(the one Viper mentioned), which can insert/extract .dds files, as well as extract them into their original formats(bitmap or targa) from the .CDDS for editing and compress them back into .dds format before inserting them into the .CDDS again.

 

BTW - if you are working on editing a skin(after you have uncompressed it into bitmap or targa format using the above tool), you can check how it looks in the sim without having to convert it back into .dds format and insert it into the CDDS - instead simply put the texture into the TempTextures folder, and the sim will load it from there.

 

The MiG skin you refered to on the lockon.ru website is not an actual skin, but a layered template - i.e a tool for making one. You can download and open it e.g. with PhotoShop or PaintShop Pro and make yourself a nice looking custom MiG-29 skin. It works by seperating varies elements of the texture - such as rivets into seperate layers, so that you can paint the base colour and then just add all the details afterwards. :)

 

Hope this helps.

 

Cheers,

- JJ

JJ

Posted

Use the LoTextureTool2.0 is the best way! :D

 

greetings

Best Regards

Viper

sigpic3353_7.gif

System: Intel Core i7-4790, 3,6GHz, 16GB RAM, 128GB SSD, 2TB HDD, NVIDIA GeForce GTX 960 2GB GDDR5,

TM HOTAS Warthog;(MSFFB2 for testing); TrackIR4 +Track Clip Pro; Windows 10 Pro.

Guest ThomasDWeiss
Posted

Where can it get it ? Link please.

Posted
Thanks ! :)

 

I hope it help them! ;)

 

greetings

Best Regards

Viper

sigpic3353_7.gif

System: Intel Core i7-4790, 3,6GHz, 16GB RAM, 128GB SSD, 2TB HDD, NVIDIA GeForce GTX 960 2GB GDDR5,

TM HOTAS Warthog;(MSFFB2 for testing); TrackIR4 +Track Clip Pro; Windows 10 Pro.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...