Roi Danton

I have contrary experiences. Before I finish the video in e.g. AfterEffects I only use uncompressed files. Indeed resulting files are big b/c every single frame is saved in it's full resolution (filesizes of 100GB, or 200-300GB for HD content are common) but I don't see the point that quality would be worse when using no compression codec. Generally, compression should be the very last step in video editing, even though archiving the video with x264/Quicktime H.264/XviD codecs and using high bitrates is a valueable method to store movies without having to worry to loose much quality (in the case you'll edit and compress the video again at a later time).

In Newview attach the ResetView option to NUMPAD5 and this key will become your best friend.

I will share my skins as ModMan v5 files thx to Ezor's updatecfg.exe. Tho the mip-map bug with custom cdds archives is still present (custom mip-maps aren't taken into account by the game). Hopefully this will be fixed in BS (or replaced by a Su-33 .lom model with .skins file ;) )

Thx for this file, this has saved my day - at least half, the texture problem on LOD change remains like for all custom skins which don't replace (not only override) original texture files.

How's going with ModMan 6? Furthermore I want to use the LUA/CFG management for a mod (ModMan v5). But this function doesn't seem to work at all?

The models looking very good! On the other hand I'd wish that the developers taking care of advancing existing aircraft models to new .lom format instead on focusing on ground models that much (e.g. current Su-33 texture placement is buggy in some areas). Or equip one or two flyable aircraft with similar accurate physics like that of the Su-25T (Su-33 & F-15).

Creating skins with ModMan isn't satisfactory, too. The advantage - replacing original texture automatically - only works if the original texture has the same size like the texture to be replaced. Mostly original textures are in 512x512 or 1024x1024 so almost all Su-33 files won't be replaced. Instead they are copied to the TempTextures folder by ModMan which causes the old problem of changing textures ingame (and lower game performance in comparison to dds files). So for sharing textures ModMan isn't better in most cases than pure bmp files. Custom cdds archives offers best performance/file size but for new users they are tricky to install.

Seems to be only "bug-free" with replacing original texture file, many skins affected Archive added to graphics.cfg TextureCollections { highFolder = ".\\Bazar\\TempTextures\\"; common = ".\\Bazar\\Terrain\\Surface\\High\\LandTexturesBMP.cdds"; common = ".\\Bazar\\Terrain\\Surface\\High\\LandTexturesTGA.cdds"; spring = ".\\Bazar\\Terrain\\Surface\\High\\LandTexturesSprBMP.cdds"; spring = ".\\Bazar\\Terrain\\Surface\\High\\LandTexturesSprTGA.cdds"; common = ".\\Bazar\\Terrain\\Surface\\High\\LandTexturesSumBMP.cdds"; common = ".\\Bazar\\Terrain\\Surface\\High\\LandTexturesSumTGA.cdds"; autumn = ".\\Bazar\\Terrain\\Surface\\High\\LandTexturesAutBMP.cdds"; autumn = ".\\Bazar\\Terrain\\Surface\\High\\LandTexturesAutTGA.cdds"; winter = ".\\Bazar\\Terrain\\Surface\\High\\LandTexturesWinBMP.cdds"; winter = ".\\Bazar\\Terrain\\Surface\\High\\LandTexturesWinTGA.cdds"; common = ".\\Bazar\\Terrain\\Surface\\High\\MapTexturesBMP.cdds"; common = ".\\Bazar\\Effects\\EffectTexturesTGA.cdds"; [b]common = ".\\Bazar\\World\\su33takera.cdds";[/b] common = ".\\Bazar\\World\\TexturesBMP_weapons.cdds"; common = ".\\Bazar\\World\\WorldTexturesTGA2.cdds"; common = ".\\Bazar\\World\\WorldTexturesTGA.cdds"; common = ".\\Bazar\\World\\WorldTexturesBMP2.cdds"; common = ".\\Bazar\\World\\WorldTexturesBMP.cdds"; common = ".\\Bazar\\World\\WorldTexturesBMP1.cdds"; common = ".\\Bazar\\World\\ShipTexturesBMP.cdds"; common = ".\\Bazar\\World\\ShipTexturesTGA.cdds"; common = ".\\Bazar\\World\\CockpitsTexturesBMP.cdds"; common = ".\\Bazar\\World\\CockpitsTexturesTGA.cdds"; common = ".\\Bazar\\Effects\\effects.cdds"; common = ".\\Bazar\\World\\Cockpit-SU25T-TexturesBMP.cdds"; common = ".\\Bazar\\World\\Cockpit-SU25T-TexturesTGA.cdds"; common = ".\\Bazar\\World\\WorldTexturesTGA1.cdds"; }I've uploaded a dark skinfile, archive created with CDDS Studio the way I did it all time. It would be kind if you could check it. Maybe I did a mistake while creating the archive - though by browsing with ModMans CDDS browser the available mip-maps are the same like in the original cdds files. -> http://files.takera.net/su33debug.cdds I've tested other dds skins, but mostly I got the message during installation with ModMan/LoMan Due to the fact that they are added as bmp files the problem occurs by using these skins (e.g. this or this), too. Instead, this skin hasn't the problem of changing in distance. Reason: The file MIG-29G-PAINT-L3.BMP is replaced in the ShipTexturesBMP.cdds by installing it through ModManager. Conclusion: It seems as replacing skins in original files is the only solution to avoid the "changing skin problem in distance" (easily possible with ModMan v5). The problem occurs by bmp files in TempTexture as well as own CDDS files (maybe you can disprove the last fact :) ). That also means most of custom skins are affected (wondering why this hasn't been encountered before).

Ah, ty for clarification of that. :) I've stored the skins in one custom cdds archive and added the archive to the list in the graphics.cfg. I have created the archive with the tool mentioned here and mip-maps were inserted by the tool, too. File with one Skin: Save textures 2 ..Level 0: 2 textures : Level 1: 2 textures : Level 2: 2 textures Now the problem still occurs (skin changes to default at certain distance) so using this method ... ... seems to be the only solution? (I don't like to change original files 'cause I want to give the skins away to squad mates) :( So every custom skin should be affected ... I'll have a look at other dds skins.

I am interested especially in the formation training. Unfortunately I'll only have time sunday evening local time (UTC+1) this weekend.

If you have Blender (OpenSource), Maya, 3DSMax or similar 3D Modelling program render a spotlight with a lightfog or other volumetric shader attached.

Thanks for the link, but I already read this tutorial (a while ago). Su-33, own skin, resolution 2048x2048. The problem occurs by using dds files as well as by using 24bit bmp files from TempTexture folder. On bright/blue skins the problem isn't visible that clear like on dark skins (b/c the default skins are all brighter). Though I still have to test out if the game behaves the same with 512x512 or 1024x1024 skins it would be nice to know if/how it is possible to use the skin in different resolutions at the same time (I think this would solve this problem 'cause it just seems to be a LOD thing) - e.g. when you open WorldTexturesTGA.cdds you have a High, Medium and Low column with similar named textures in each column.

Hello all, I've got a problem with custom 2048-Skins. Above a certain distance the custom skin is replaced by the default one. Do you know a workaround, maybe adding the same Skin in several resolutions? If so, how to do this? Thanks, Roi

What F-15 model/skin is that? The engine looks awesome.

Thats right, but you only can achieve this in a team and someone in this team has to be familiar with the techniques very well. Technique knowledge comes first so you know how to realize your ideas best and in an affordable time.

Fortunately the memory prices have fallen so much. With only one GB editing sucks. ;)

;) Okay, thx for the clarification! So the only chance would be to make a new Su-33 model which uses skins files. :/

There must be a way because it is possible for the Su-25T, Su-39 and a custom F-15C model (as I can remember) as well.

With Su-25T I can edit meinit.xml and its .skins file to add a new skin slot to the list. For the Su-33 there doesn't exist a .skins file but maybe there is another way I can add a new skin slot? (if I only edit meinit.xml there appears a new slot but if I choose this Skin Slot the plane appears without a skin as expected)

Incredible! Incredible work. Thanks for sharing!