Jump to content

western_JPN

Members
  • Posts

    481
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by western_JPN

  1. Thanks your new information here. I try it in my PC environment of ... then DS passes user auth process and main window is opened. But No response to Web GUI and at last DS crashes when I click the DS window. dcs.log is here. I wish ED debug team can reproduce our DS crashing ...
  2. My B600 tug skinpack is replaced as Rev2. Added 8x skins. -2x new colors -2x Air France , -USAir , -US Airways -AviaPartner , -TGS
  3. I've installed ob DS newly and tested. Common OS environment : Windows 10 Pro Language = Japanese / Japan Windows' setting 1 : Keyboard = English / US DS running OK. Joining from a client and fighting a mission OK. Windows' setting 2 : Keyboard = Japanese / Microsoft-IME DS running OK. Joining from a client and fighting a mission OK. Windows' setting 3 : Keyboard = Japanese / Google-IME DS crashing before user auth in splash screen time. Its full log --- So, the crashing looks related to Windows' Language - Keyboard settings. In this time I don't change Windows' Language from Japanese to some other though, Perhaps Language = English / US or UK + Keyboard = English / US or UK (without any 3rd party Input Method Engine) maybe OK for DS.
  4. Thank you, HawaiianRyan ! After applying your CAM_Light lua released on 1st/Jan. , Cessna 210N problem looks solved.
  5. I find another behavior about today's ob crashing. I use Google Japanese Input Method Engine (IME) to type Japanese letters. It makes the problem. When I switch Windows 10's Japanese IME setting from Google IME into Microsoft IME, DCSW 2.8.2 ob client becomes to open without crashing. I hope my information helps ED staff to fix it. About its crashing time, my 1st post dcs.log with 21 lines is the full. /bin/CockpitBase.dll is its last.
  6. umm ... Do you use some Input Method Engine to type non-alphabetical letters ? I find Google Japanese IME causes my client crashing, but Microsoft J-IME doesn't. Not Japanese , Not client , your environment maybe much different from mine though, the cause maybe around Windows' Language setting or Keyboard Input setting. I hope ED will solve this problem DCS client and server can run with any Language or IME again.
  7. When I try to install a fresh 2.8 ob install by current DCS_World_OpenBeta_web.exe , even Full installation is selected and Caucasus terrain is contained in Setup screen, DCS Updater 2.16.2.17 failed to install Caucasus and DCS World doesn't have Caucasus map after finishing the installation. I can add Caucasus later by Module manager in DCSW client and it's not serious. But it makes confusing for beginners and maybe a bug against the design of web installer.
  8. Hi, Invisibull. I experienced similar crashing on my PC (mine is DCS World 2.8.2.35632 ob client; instead of its server), the final log line is the same about /bin/CockpitBase.dll . I reported my trouble in another topic Temporary I switch Windows 10's Language setting into English / United States from Japanese / Japan, then the crashing was solved. If you can try to change your Language setting of the Windows , test it, even not good solution though ...
  9. DCS World 2.8.2.35632 ob crashes between splash screen, doesn't reach main window. dcs.log is here I thought this crash is caused by Windows 10's Language setting. I set my Windows 10 in Japanese (multi-byte characters language used in Japan). Once I switched Windows 10's Language into English / United States .... solved. No crash, Main windows comes and I can fly missions.
  10. Hi, crazyeddie. Those odd triangles can be seen in ModelViewer and some uv glitch / polygon glitch to be fixed might exist there, I also think. Only temporary solution and not creative, those uv are on the same R11_Frame.dds somewhere instead of different texture file. When I paint ALL area of R11_Frame.dds in yellow, its result is here. To find where uv ? umm... that's another trouble. Panel Finder work or ... ?
  11. Those words choice are .... a bit confusing between "in US / in English" or "in Japan / in Japanese" about F-15J/DJ. Based on Japanese publishing, F-15J/DJ are separated in those two groups. Pre-MSIP : Lot C1 - C5, 98x J + 12x DJ, delivered between 1981 - 1984, no modernized (except 1x J), carrying only AIM-7/9s as AAMs first, AAM-3 capability was added after. J-MSIP : Lot C6 - C-17, 67x J + 36x DJ (+ 1x J modernized from Pre-), delivered between 1985 - 1999, modernized many times, carrying AAM-3/4/5 or AIM-120 after modernized. So, no modernized Pre-MSIP group is a bit majority in JASDF F-15J/DJs. Their first built designs were almost same to basic (un-modernized, before MSIP-2) USAF F-15C/D. Difference was RWR and Datalink as F-2 said; they are small things. Later changes were also minimum .... only AAM-3 capability and replacing F100 engine ?
  12. ahhhh ... I missed some advices posted here (or there) past .... Someone experienced that ? in executing CAM (Cessna 210N is installed as AI only) + RAT missions , one 210N born at an airport opens its left door and taxi to the runway, it keeps the door opened and stops on the take-off position of the runway (perhaps AI wait to close the door before accelerate, but it's never done), the runway is blocked minutes and other planes waiting on taxi ways after the 210N. Are there some solutions making 210N AI not to open the left door or close it before taxing ?
  13. western_JPN

    A-7D

    External shape's differences are almost so. When A-7D will be made as flyable, cockpit instruments positions are quite different between D or E.
  14. Their combat ranges were ..... A-7 with 30x mk82 means no external drop tanks ---- with heavy weight and high drag ---- might become very short combat range; one of the "light attack" essence. And B-52 was designed for a strategic bomber; very long range flight with nukes or nuclear warhead ASMs instead of conventional bombs. Btw, standard B-52s can carry 27x mk82 inside their fuserage bomb bays and after 1964, B-52s were modified to carry 24x external bombs via MERs --- so total 51x mk82 over A-7s. Current (old 3d model) DCS's B-52H AI simulates this style. Another Big Berry modification was done on B-52D for Vietnam war making that fuserage bomb bays can carry 84x mk82. That was nearly 3x A-7's amount mk82.
  15. I've completed my paint works for B600 tug. The skinpack is uploaded to User Files section. Please wait ED staff's review.
  16. Hi, Massun92. Thanks for the great assets. I'm trying to retouch your TUG texture as civilian airlines' liveries like ...
  17. CAM + TTTwJ and ...
  18. Do you read "FAQ and Updates" topic pinned in this Sinai Map section ? From OnReTech's 1st post : Both of Ben Gurion and Cairo international airports are planned in the second phase of the map development. On 06/Oct./2022, He posted airports / airfields marks.
  19. USAF C-9A Nightingale, VC-9C "Air Force Two" skinpack is published here : https://www.digitalcombatsimulator.com/en/files/3328235/ This skinpack contains 14x C-9A skins + 3x VC-9C skins. My screenshots posted one and three above show this pack's contents.
  20. This C-9A is not "Air Force Two" one, but NATO VIP transport. VC-9C's paintscheme is similar to this 71-0876 and I'll add it easily. I try to change its belly's blue into more bright like B747-AF One.
  21. Hi, Shubunkin. When you are talking about A-10C Warthog or Ka-50 Black Shark 2 modules, they have been fully updated into new named modules as A-10 C II Tank Killer and Ka-50 Black Shark 3. Old Warthog and BS2 modules were stopped to sell on their released days.
  22. Hello, everyone. I'm happy you are interested in my mod. Now I try to add more USAF Nightingale liveries .... 1980 ones, early 1990 ones, "UNITED STATES OF AMERICA" lettering ones deployed to NATO and no Red Cross tail ones.
  23. US Navy C-9B (DC-9) Skytrain-II skinpack is published here : https://www.digitalcombatsimulator.com/en/files/3328148/ This skinpack contains 17x Navy C-9B + 3x leased DC-9 skins with 12x squadrons' tail codes (JS/JT/JU/JV/JW/RS/RT/RU/RV/RW/RX/RY).
×
×
  • Create New...