western_JPN

I've tested different versions of EDM Exporter on fixed version Blender 3.3.11 with Fisherman82's example .blend file as a new Windows User account and installing on new drive/folder (avoid setup contamination). EDM Exporter 1.0.6 and 1.0.7 --- "Disable in Renders" action is exported to .edm EDM Exporter 1.0.8 and 1.0.12 --- "Disable in Renders" action is NOT exported to .edm (always rendered) Those results look like EDM Exporter's trouble in version 1.0.8 and laters. I'll move those reports to Tobi's exporter developing topic. Thank you.

Yes. My blender + EDM exporter shows that behavior with your example .blend files. Some little little setup item I missed or mistook, I don't know what I forgot to do or did not to do.

Thanks your supports, Fisherman82. I remember one thing I felt strange about my Blender working... Besides animation and actions, object list panel's "Disable in Renders" button (Camera Icon) or "Renders" checkbox in Visibility panel are ignored. When I set EDM panel's Render Type column as "RenderNode" , the part is always exported as rendering polygons, even Visibility Renders check is Off or Disable in Renders Camera Icon clicked. I have to change EDM - RenderType column into "none" when I want not to export the part in .edm . I missed some setup page in blender to enable / disable those Renders control UI ?

With these great helps of Fisherman82 , I got those exterior lights on my models in DCS. I've sent a private message to him, same trouble report here again. Position lights and Logo lights don't animation in DCS. My exported edm files don't contain the argument number 69 to turn-on/off those lights. Those lights are always On in DCS. "Disable in Renders" action is not exported in my environment ; Blender 3.3.11 + Tobi's EDM Exporter 1.0.12 . Something mistaken by me in setup / operation Blender or Exporter .... but I have no idea. Old versions' set --- Blender 2.93 + Exporter 1.0.8 --- was the same. I have to solve this problem before publish a new version. Cabin interior lights in the screenshots are a fake gimmick. Under airport light towers or sunset glow, a bit strange feeling will come ; but I cannot do anymore about it. They'll keep as is to the publishing time.

I've also faced 400 auth error today and yesterday , two or three times per one day (perhaps 20 or more times per day DCS.exe is executed by me). For me and my DCS environment, repair is not needed to solve that 400 error. Only wait some minutes. After it, executing DCS.exe without any other operations, DCS starts normally with correctly passed online user auth and all purchase modules available. Serious problem of 400 error is --- it prohibits switching to Offline mode. I cannot use any purchase modules (aircrafts or terrains) even in three days offline limits.

Done. Someone knows the reason that OAI painted three 767s ( N423AX, N441AX, N495AX ) in business jet like color scheme ?

wip test shot My other models ( DC-9 / MD-80 , ERJ-145/135BJ ) are not made their polygons separated as cram-shell / open-able their reverser doors. When I'll rebuild 3d polygons .... umm

+1

Yeees. It's in my plan preparing the livery in the pack's 1st release. The free shared OAI logo vector data is broken about its aircraft silhouette part. I have to retouch the data before pasting as the texture. Btw, promised livery list in the 1st release --- -200 = Aer Lingus 2016, ANA (Domestic), Air Gabon, Ansett Australia 1991 + 1996, Birgenair, CAAC, Delta 2002, Malev, US Airways, UTair, Vietnam Airlines 1995 -300 = Air Canada rouge, Air China, Air Europa 2010, Air Europe 2005, ANA 1988 - 2018 (D + I), Ethiopian Airlines 2011, Garuda Indonesia, Israir, Japan Airlines 2019, LTU, Martinair 2010, neos 2011, SAS 2002, Star Alliance (Air Canada), Thomsonfly 2007, Turkmenistan Airlines 2009, WestJet I cannot promise I'll finish all of them before the 1st release date, those liveries are planned --- (Pax) Aero Mexico, Air Astana, Air New Zealand, American Airlines, Atlas Air, Delta (-300), El Al, KLM, Kuwait Airways, some-of LAN / TAM / LATAM, Las Vegas Sands, LOT, North American, United, VARIG, Vietnam Airlines (-300) (Freighter) ABX, Amazon Prime, Amerijet, ATI, TMA Cargo, West Atlantic Sweden (Government or Air Force) Chile, Israel, Kazakhstan I'm wondering ... Freighter liveries of DHL / FedEx / TNT / UPS are already in DCS / CAM ; not so needed ? priority low.

Hi, Guys ! I keep this topic for "T-Tail Twin Jets" only. (in far future, expanded to T-Tail Triple Jets ? far far far ... ) I post another topic(s) for different style AI aircraft mods. Please agree with my opinion here.

Boeing 767 mod AI only , version 0.1.1 beta , on 29/Jan/2025 updated. Download : https://www.digitalcombatsimulator.com/en/files/3342692/ All 3d and 2d works are done by me. Current contents are only civil airliner -200/-300 variants. Military Tanker KC-46 Pegasus will come after 4 - 10 months. This pack contains 30x B767-200 and 31x B767-300 liveries. Known issues --- No damage models. LOD models are not good. Wing root shape has to be retouch. Some animation bugs (main wheel bay doors opening animation etc.). Skins don't have weatherings or details. No normal map textures. Airlines' windows closing arrangement + shades down options aren't drawn. No Freighter liveries. Liveries list of B767-200 : Aer Lingus, Air Gabon, All Nippon Airways, American Airlines, Ansett Australia, Birgenair, CAAC, Continental Airlines, Delta Air Lines, Iraqi Airways, Jordan Aviation, Kam Air, MALEV, Omni Air International, SilverJet, South African Airways, TWA, USAirways, UTair, Vietnam Airlines. Aeronexus, Comlux Aruba, MidEastJet, Sheikh Mustafa Edrees, Vision Airlines, Weststar. Kazakhstan Government. Liveries list of B767-300 : Air Canada rouge, air astana, Air China, Air Europa, Air Europe SpA, All Nippon Airways, Delta Air Lines, Ethiopian Airlines, Garuda Indonesia, Israir, Japan Airlines, LTU, Martinair, neos, Omni Air International, SAS, Star Alliance - Air Canada, Thomsonfly, Turkmenistan Airlines, United Airlines, Vietnam Airlines, WestJet.

Hi. About too quick ground turn, possible lua script problem. tand_gear_max = value --- how about 3.73 ? And main_gear_pos = {,,} and nose_gear_pos = {,,} . When thier position values (especially the 1st column Y-axis value) are incorrect and two pos are too nearer than historical 3d shape , such too quick ground behavior might come. pos values in { , , } format in lua is to be written in the order { Y , Z , X } instead of { X , Y , Z } as described in DCS modding guide pdf.

Hi. About Hawk T.1, old VEAO's Hawk T.1A is still available in DCS World v2.8.8 as AI plane or static plane. Others are not seen by me.

Isn't it upgrade price for 1944 users ? When I log-out my account from ED website before opening terrains' store page, Normandy 2.0 price tag becomes $ 47.99 .

I use EDM EXPORTER for Blender by Tobi about this project. Blender modding has less document than 3ds Max , or DCS environment becomes something outdated from the time of sample models / scripts / instruction movies were published. I've tried, but never succeeded those lights working properly. Someone shows me Blender Exporting techniques of lights available on current DCS. When I'll succeed to implement external lighting on my models, tail logo light will become possible. I don't know what named 3d lighting function matching the logo light ... umm ... Cabin light is --- perhaps not impossible --- also not easy. I'll think something I can do. Thank you.

Thanks, BIGNEWY !!

About F/A-18C , the same name of the flyable module's F/A-18C Lot 20 is needed to use the same liveries on static planes. No need to touch bazar folder or coremods folder.

aaahhh ... If talking about those A300 or B737 models in NTTR / PG maps --- No easy way to change textures of those map objects. Smart solution is --- Erasing them from the map by mission editor trigger function (NTTR map needs tricky lua script) and place CAM / MAM or official planes with liveries you like.

In version 2.8 updated time ? (I don't memorize correctly when) , ME file loading dialog was added the new function 10x file full-path history. This function is much useful in try and error for lua scripts, especially the files are placed outside of the current (or default) folder. Then I hope this 10x history function reworking more. Current 10x history is only one database and path names of both *.miz files and *.lua files are recorded as mixed. Even opening or loading a *.miz file dialog, some history items are *.lua files. In the other hand, loading a *.lua script time --- some history items are *.miz files. Will ME have two history database each 10x for "*.miz" or "*.lua" and show one of them matching the dialog loading miz? or lua?

Static objects of --- fixed-wing planes, helicopters, ground vehicles (tanks / SAM and AAAs / unarmed cars), animals, structures --- have the common "Paint Scheme" system to their Live units. Static planes placed on an airfield or static helicopters on a carrier deck can be wear the same skins of their moving aircraft / helicopter units. The same skin files in user Liveries folders are also called by the static variants. Ships and cargos, "Airfield and deck equipment" static objects don't have the function in current v2.8.8's ME system, though.

Current Hatzor AFB is used for only Beechcraft King Air or Bonanza by IDF. Any F-15s or F-16s aren't assigned there. Rearming might not be planned. If you want to play fictional missions F-15/16s takeoff from / land to / rearm at Hatzor , tents or other ground objects can be erased by Mission Editor Trigger function. From google's satellite photos, Hatzerim's spots 10 - 103 might be (or should be) taxi through ones. Current module design looks a bit buggy ? Those tents maybe misplaced too west, to be moved to east. Open spots 111 - 119 are also taxi through rearming area IRL, only taxing lines are missing in the module. We can rearm on spots 111 - 119 and 138 - 141 until future module retouch.

Even AIs don't behaves so, Each AFBs in Sinai map have about eight or sixteen "taxi through designed" HAS spots / Tent spots , or open rearming spots. Player may use those spots to rearm.

In my memory, TACAN A/A Station is a special function only Tankers equip. F-15E might not have Station function IRL. In DCS mission editor, F-15E's "Activate TACAN" command becomes gray-out even added, not enabled. Maybe a historical behavior. Impossible F-15E chasing another F-15E by TACAN.

I don't know historical fixed-wing a/c taxi routes of Tel Nof around helicopters apron (spots H18 - H27). I think fixed-wing a/c doesn't enter the apron to avoid ground staff / helo pilots injury. More research about historical taxi operation in Tel Nof is needed. When my thought is fitted IRL .... those fixed-wing a/c taxi routes "short cut" the helicopters apron H18 - H27 in current Sinai module have to be changed.