NRG-Vampire

ok. teaser :smilewink: http://postimg.org/image/e6chy6vxx/ http://postimg.org/image/kwy14qpf9/

there is a reconditioned Crimea map for DCS (more accurately: an extended Black sea map with parts of Turkey, Bulgaria, Romania, Moldova, Armenia and Azerbaijan more) but unfortunately that's not available to the public momentarily

:thumbup: do not make the mistake like Kinney Interactive did 3 years ago: given that only two weeks of their DCS:F-35A kickstarter campaign people need time to hear about your project so just choose a long time campaign and set the deadline for 60 days at least, imho

seems that's your model Skate :D like this http://forums.eagle.ru/showthread.php?p=2378606#post2378606

fine :thumbup: thanks

i downloaded it 2 hours ago f-5e, f-5e3 and fw-190: checked all countries what use those aircrafts (only default skin visible) p-51 and tf-51: checked all countries (mainly usa and russia have few skins what do not change but few others skins are ok - and have weird specular silver lights on many skins too)

v1.6 in 1.5.3 i have problems with f-5e, f-5e3 and fw-190: skins do not change at all p-51 and tf-51: only few skins do not change others ok

oops, uh-1h and mi-28n does not show livery changing :( others are ok to me

your welcome by the way, rope length not visible for choppers so you should use this for me_payload_panel.dlg at line 225 for normal window ["staticPicture"] = { ["children"] = { }, ["params"] = { ["bounds"] = { [1] = { ["h"] = 216, ["w"] = 373, ["x"] = 1, ["y"] = 424, for larger scrollable window ["staticPicture"] = { ["children"] = { }, ["params"] = { ["bounds"] = { [1] = { ["h"] = 366, ["w"] = 366, ["x"] = 1, ["y"] = 424,

all helicopters work aircrafts work: a-10a, bf-109, c-101, e-2d, f-15e, f-5e, hawk, m-2000c, p-51, tf-51, an-26, il-78, mig-21, mig-29g, su-25, su-25t, su-27, su-33, yak-40

tried in 2.0.2 unfortunately does not read liveries of A-10C, F-15C, F-5E3, F-86, F/A-18C, L-39C/ZA, MiG-15/21/29 etc. ok. thanks

by the way, unfortunately i did not download the 1.0 version in time so how can i freeze the camera when/after i changed the livery - i would like to try that - instead of resetting the camera view angle and distance

maybe LiveryManager with setLiveryHandle function ?

so i think you should implement that arg70-id number usage to you me_payload.lua file first- model viewer use that too to read textures of old models

only old/index based skins use the id number from the description.lua file (old models use the arg70 coz newer models do not have arg70 skin-visiblility, however you can add id number usage to the description.lua if animations or visibility is set to arg70 in 3dsmax to new models) id number usage is good to over the arg70 value 1.0 too (for new user-made skins) for example if you add new skins with numbers in the texture dds file name then id=14 will load texture name with "tex-name-14" however that's not the same if a built in skin (in the 3D model) use the arg70 value 1.4 old models use 10 textures (or maximum 11 if it defined in the 3d model file "inside") but you can load textures from "outside" as well - see above - LOM models used the "skins" extension for this too

yes, those old models use arg70 for sinks arg70 value 0.0, 0.1, 0.2 and so on - that's the id number in the description.lua file however the modelviewer able to read skins both way: from description.lua by material and texture names and from description.lua by id number - that read the 3d model texture names what connected to arg70 skin-visibility so can you implement that arg70 value changes/variable usage into your lua file ? (if not we can convert that old arg70 skin names texture usage to a description lua file - how newer skins/liveries works - but this "conversion" needs some time unfortunately)

unfortunately old models (such as F-14, F-16, MiG-23, MiG-29S etc.) does not show changed skins. only default skin visible :(

rep sent :thumbsup: great job :bounce:

WOW :thumbup: it's wonderful ! great job Mario :thumbsup:

:worthy: oh man, this ▲ sounds f**king awesome and professional :bounce: i believe you will really shorten that monstrous c++ development time :thumbup:

today i was allowed to show some oldies various screenies

roger that. thanks Dmitry. im waiting for that tool :thumbup:

is that official tool already available ?

i have no problems with shadows at all trees are few polys only, those use only one texture (caucasus) new trees (nevada) use few textures only (2-3 textures iirc) moreover we have fixed tree models/materials around caucasus buildings so those have shadows again without fps loss

honestly guys, what's the problem with tree shadows ? need/eat some fps ? or ugly and simply you don't like those? imho those are parts of the realism