Jump to content

legitscoper

Members
  • Posts

    164
  • Joined

  • Last visited

1 Follower

About legitscoper

  • Birthday 05/04/2002

Personal Information

  • Flight Simulators
    SU-25T, AJS37, SU-27
    EF-2000 (soon)
  • Location
    my house
  • Interests
    Programming, Games, Electronics

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. yep, it's just that you see the max possible range, but the TV sensor still needs a lock. Sometimes it never locks, especially at night
  2. Well it depends on how much information we have about it, and if it fits the model HB is making. So I doubt it will come really, maaaaybe years after release...
  3. I'm attaching the mission file which I used. I tried removing one of the F-16s, testing if it is same for other aircrafts. Edit: removing apache, or hornet on Prince Hassan, same effect. Seems like this is the only airfield that has problems Edit2: removing apache from King Hussein Air College doesn't crash the editor. Removing F-16 from KHAC, Tiyas, or Ramat David also doesn't crash it. Edit3: Also I can't even get rid of the aircrafts by swapping them to another unit, and then going back to original one, still same issue Edit4: found this in log: 2024-08-15 14:21:01.350 ALERT LUACOMMON (Main): Error: GUI Error: [string "CoreMods\aircraft\F-16C\Datalinks\Link16.lua"]:378: attempt to index field '?' (a nil value) GUI debug.traceback: stack traceback: [C]: ? [string "CoreMods\aircraft\F-16C\Datalinks\Link16.lua"]:378: in function 'init' [string "./MissionEditor/modules/me_datalinks.lua"]:278: in function 'applyDescriptor' [string "./MissionEditor/modules/me_datalinks.lua"]:237: in function 'update' [string "./MissionEditor/modules/me_datalinks.lua"]:103: in function 'setData' [string "./MissionEditor/modules/me_mission.lua"]:1983: in function 'fixDatalink' [string "./MissionEditor/modules/me_mission.lua"]:2502: in function 'load' [string "./MissionEditor/modules/me_mission.lua"]:4866: in function 'save' [string "./MissionEditor/modules/me_mission.lua"]:4779: in function <[string "./MissionEditor/modules/me_mission.lua"]:4762> (tail call): ? [string "./MissionEditor/modules/me_toolbar.lua"]:738: in function 'saveMissionFileDialog' [string "./MissionEditor/modules/me_menubar.lua"]:756: in function 'func' [string "./MissionEditor/modules/me_menubar.lua"]:266: in function 'onChange' [string "./dxgui/bind/Menu.lua"]:26: in function 'callback' [string "./dxgui/bind/Widget.lua"]:375: in function <[string "./dxgui/bind/Widget.lua"]:370> 2024-08-15 14:21:01.389 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [1920, 1080] Same goes when I try to remove other aircraft with datalink, like A-10C, also on Prince Hassan 2024-08-15 14:27:36.025 ALERT LUACOMMON (Main): Error: GUI Error: [string "CoreMods\aircraft\A-10\Datalinks\SADL.lua"]:285: attempt to index field '?' (a nil value) GUI debug.traceback: stack traceback: [C]: ? [string "CoreMods\aircraft\A-10\Datalinks\SADL.lua"]:285: in function 'init' [string "./MissionEditor/modules/me_datalinks.lua"]:278: in function 'applyDescriptor' [string "./MissionEditor/modules/me_datalinks.lua"]:237: in function 'update' [string "./MissionEditor/modules/me_datalinks.lua"]:103: in function 'setData' [string "./MissionEditor/modules/me_mission.lua"]:1983: in function 'fixDatalink' [string "./MissionEditor/modules/me_mission.lua"]:2502: in function 'load' [string "./MissionEditor/modules/me_mission.lua"]:4866: in function 'save' [string "./MissionEditor/modules/me_mission.lua"]:4779: in function <[string "./MissionEditor/modules/me_mission.lua"]:4762> (tail call): ? [string "./MissionEditor/modules/me_toolbar.lua"]:771: in function 'saveMission' [string "./MissionEditor/modules/me_menubar.lua"]:688: in function 'func' [string "./MissionEditor/modules/me_menubar.lua"]:266: in function 'onChange' [string "./dxgui/bind/Menu.lua"]:26: in function 'callback' [string "./dxgui/bind/Widget.lua"]:375: in function <[string "./dxgui/bind/Widget.lua"]:370> 2024-08-15 14:27:36.069 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [1920, 1080] 2024-08-15 14:27:38.400 ALERT LUACOMMON (Main): Error: GUI Error: [string "./MissionEditor/modules/me_mission.lua"]:7619: attempt to index field 'mapObjects' (a nil value) GUI debug.traceback: stack traceback: [C]: ? [string "./MissionEditor/modules/me_mission.lua"]:7619: in function 'scale_group_map_objects' [string "./MissionEditor/modules/me_mission.lua"]:7538: in function 'scale_mission_map_objects' [string "./MissionEditor/modules/me_map_window.lua"]:2308: in function 'setZoom' [string "./MissionEditor/modules/me_map_window.lua"]:2289: in function 'onMouseWheel' [string "./dxgui/bind/NewMapView.lua"]:395: in function 'onMouseWheel' [string "./dxgui/bind/NewMapView.lua"]:30: in function <[string "./dxgui/bind/NewMapView.lua"]:29> (tail call): ? This happens when I keep clicking the "show models" button 2024-08-15 14:39:00.550 ALERT LUACOMMON (Main): Error: GUI Error: [string "CoreMods\aircraft\FA-18C\Datalinks\Link16.lua"]:363: attempt to index field '?' (a nil value) GUI debug.traceback: stack traceback: [C]: ? [string "CoreMods\aircraft\FA-18C\Datalinks\Link16.lua"]:363: in function 'init' [string "./MissionEditor/modules/me_datalinks.lua"]:278: in function 'applyDescriptor' [string "./MissionEditor/modules/me_datalinks.lua"]:237: in function 'update' [string "./MissionEditor/modules/me_datalinks.lua"]:103: in function 'setData' [string "./MissionEditor/modules/me_mission.lua"]:1983: in function 'fixDatalink' [string "./MissionEditor/modules/me_mission.lua"]:2502: in function 'load' [string "./MissionEditor/modules/me_mission.lua"]:4866: in function 'save' [string "./MissionEditor/modules/me_mission.lua"]:4779: in function <[string "./MissionEditor/modules/me_mission.lua"]:4762> (tail call): ? [string "./MissionEditor/modules/me_toolbar.lua"]:771: in function 'saveMission' [string "./MissionEditor/modules/me_toolbar.lua"]:784: in function 'onChange' [string "./dxgui/bind/ToggleButton.lua"]:20: in function 'callback' [string "./dxgui/bind/Widget.lua"]:375: in function <[string "./dxgui/bind/Widget.lua"]:370> 2024-08-15 14:39:00.585 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [1920, 1080] 2024-08-15 14:39:45.591 ALERT LUACOMMON (Main): Error: GUI Error: [string "./MissionEditor/modules/me_mission.lua"]:7619: attempt to index field 'mapObjects' (a nil value) GUI debug.traceback: stack traceback: [C]: ? [string "./MissionEditor/modules/me_mission.lua"]:7619: in function 'scale_group_map_objects' [string "./MissionEditor/modules/me_mission.lua"]:7538: in function 'scale_mission_map_objects' [string "./MissionEditor/modules/me_map_window.lua"]:2308: in function 'setZoom' [string "./MissionEditor/modules/me_map_window.lua"]:2289: in function 'onMouseWheel' [string "./dxgui/bind/NewMapView.lua"]:395: in function 'onMouseWheel' [string "./dxgui/bind/NewMapView.lua"]:30: in function <[string "./dxgui/bind/NewMapView.lua"]:29> (tail call): ? 2024-08-15 14:39:47.264 WARNING LOG (24700): 6 duplicate message(s) skipped. 2024-08-15 14:39:47.264 ALERT LUACOMMON (Main): Error: GUI Error: [string "./MissionEditor/modules/me_statusbar.lua"]:185: attempt to index field 'mapObjects' (a nil value) GUI debug.traceback: stack traceback: [C]: ? [string "./MissionEditor/modules/me_statusbar.lua"]:185: in function 'onChange' [string "./dxgui/bind/ToggleButton.lua"]:20: in function 'callback' [string "./dxgui/bind/Widget.lua"]:375: in function <[string "./dxgui/bind/Widget.lua"]:370> 2024-08-15 14:39:47.984 ALERT LUACOMMON (Main): Error: GUI Error: [string "./MissionEditor/modules/me_statusbar.lua"]:179: attempt to index field 'mapObjects' (a nil value) GUI debug.traceback: stack traceback: [C]: ? [string "./MissionEditor/modules/me_statusbar.lua"]:179: in function 'onChange' [string "./dxgui/bind/ToggleButton.lua"]:20: in function 'callback' [string "./dxgui/bind/Widget.lua"]:375: in function <[string "./dxgui/bind/Widget.lua"]:370> 2024-08-15 14:39:48.384 ALERT LUACOMMON (Main): Error: GUI Error: [string "./MissionEditor/modules/me_statusbar.lua"]:185: attempt to index field 'mapObjects' (a nil value) syria.miz dcs.log
  4. How to reproduce? 1. Load mission with aircraft 2. Remove any aircraft 3. Mission editor bugs out, makes it impossible to save the game, corrupts the save, makes impossible to click on other aircrafts, "show models" button does not work, as attached in video. Also, save icon bugs Video: https://youtu.be/qptWAX0FVIQ
  5. After many tests, I'm announcing a new server series: The Syria Offensive, and The Kaukasus Offensive What Makes This Server Unique? This server is perfect for smaller groups of players, allowing for quick engagement in action. With average distances between FARPs being just 30-50 km (16-25 nm), you’ll be in the heat of battle in no time. nullnull Even a single player can make a big difference and change the way the campaign goes! The community is small, and thus very helpful and friendly, you will find your flight mate easily. You may already be familiar with The Caucasus Offensive—it’s been running for over 7 years. However, under new development, the server has seen substantial upgrades, including a move to better hardware. It now runs smoothly even with 16 players online. Some details about the server: Map Rotation: After each victory, the server switches to a new map. Realism Settings: External views and labels are disabled. On the F10 map, you only see your position and objectives. JTAC functions within a fog of war scenario. Challenging Objectives: Targets are heavily defended (e.g., S-300s at airfields, Roland systems, Tunguskas), so knowing your aircraft and its capabilities is crucial. High-Performance Hosting: The server is hosted in Poland on a 900/900 fiber optic connection for optimal performance. Simple, Accessible Gameplay: No overly complicated mechanics—just straightforward, engaging scenarios. Campaign info: Win conditions: enemy has got 2 objectives left. Life system, to prevent doing solo kamikadze runs, you get 5 lives. If you loose all of them, they reset in 4 hours, counting down from your first takeoff. Antenna objectives, which allows to place wild SAMs. To capture objectives, bring a CTLD crate, and unpack it. Syria mission is themed to be 1990s, most SAHRs are removed, no advanced weapons. Kaukasus mission is cold war. Scripts used in the game: CTLD - all helicopters have the option to do simulated sling loading of SAM, artillery, JTAC, and other crates. EWR script - if your team has deployed a EWR, you will get messages about any threats in the air. CSAR - rescue ejected enemy and friendly pilots, to give them their live back, and also to get some cash. AI planes - enemy AI planes spawn when you attack a objective. Convoys - when near friendly objective, send a SAM, groundcrew, or armored convoy to support it. Convoys cost money, depending on convoy type. Support aircraft: AWACS and tankers. Call them anytime, they last until server restart, they also cost you cash. The server is still under active development, feedback and bug reports are much appreciated! Thank you, and see you in skies of DCS Discord: https://discord.gg/EGV7VFuceY DCS IP: dcs.legitscoper.net Server websites*: https://tso.legitscoper.net/ and https://tko.legitscoper.net/ Look for "TSO", or "TKO" in the server browser *Server has 2 websites, but only 1 shows the correct real-time data, the one of the current campaings. If Syria is played, then Syria website is the correct to check. But the long-term statistics work just fine on both.
  6. Hello, this is I think a simple thing to add, which would really help mission developers more easily distinguish between a cannon kill, and a bomblet kill, since not knowing that causes issues, when I want to reward players for doing a hard, cannon kill, but not do that for when they go with a cluster bomb and wipe everything. For now the weapon_name for a cannon is just '', so no name, which is the same for all bullets, bomblets. Changing that to real names, like "20mm", "30x165", "MJ2 HEAT BOMBLET" etc.
  7. Same issue, players reporting black screen on my servers with external views disabled, and no f11 camera. What's interesting is, that if you go to spectators, you can see all the units anyway
  8. I think it's better to be surprised on when it releases, than be given a release date which will be postponed 5 times
  9. I know it's a difficult and very complex aircraft to make, but even 1 screenshot from cockpit or something would satisfy me to know that project didn't stall because of no data available to make it, or some other problems.
  10. Finally, thank you developers team, this is such a nice feature to mission developers who have hundreads of client slots on a 1 airfield
  11. Despite having 64 gigabytes of RAM, and a decent PC, DCS sometimes just decides to eat all available RAM, and just crash, but really only in Mission Editor. It does this only when having selected option "Show models" and zooming in on a unit group.
  12. Yeah just be patient, now they have a ton of stuff to fix in Phantom, and after that it's 90% work for eurofighter
  13. Remember, when phantom drops, they will still fix a lot of bugs, and add new features to it, so the work won't go 100% for Typhoon. But anyway, I'm not expecting it sooner than 2025
  14. Some X56 just break when using Logitech's X56 H.O.T.A.S software. When I tried to set a J-curve, after the change, when I was pulling the stick, values were jumping to max values in 2 places. Same with X axis, but even worse. The same thing can happen when you click calibration button. Here is the fix: 1. Remove the stick from base 2. Unscrew it. You will find a green board 3. Remove white board connector 4. De-solder the hall sensor chip (the one with 8 legs, pretty small, sitting next to magnet mounted on sitck). Remember it's oriention, take a picture, or just match the chip's dot indent with the printed dot on board 5. Connect white board connector, do not assemble the stick base back, not needed 6. Connect the base via USB to PC 7. Run a calibration inside the software. 8. Disconnect the stick 9. Remove the board again 10. Solder back the sensor 11. Assemble everything back. 12. Connect, and voila! It works, at least works for me, and worked 2 times. 13. Do not ever use the software for any curve settings, I use it for RGB only. You might also have a problem of having off-center axes, as it's pretty hard to solder the chip back 100% precise. In this situation you can try to adjust the board position using the 4 screws, and maybe some spacers, or use external software to tune it.
  15. This doesn't work, lights in stick never go out
×
×
  • Create New...