Jump to content

Frosties

Members
  • Posts

    110
  • Joined

  • Last visited

Personal Information

  • Flight Simulators
    Lock On Flaming Cliffs
  • Location
    Sweden
  • Occupation
    Student
  1. Yea i know, and i had started it up and got stuff in ServerSettings.lua still wouldnt start. Once i used my OLD serversettings.lua then it started, but with the new i just wouldnt start...
  2. Having some issues, the server wont autostart, it seems that the server tries to start then fails, but if i go into WebGUI and press RUN it starts up.. 2019-04-24 14:01:44.948 INFO NET: server has started 2019-04-24 14:01:48.953 INFO NET: No UPNP devices found. 2019-04-24 14:01:48.953 INFO NET: Successfully set up Dual-Stack socket, using both IPv4 and IPv6 2019-04-24 14:01:48.953 INFO NET: Listen to IPv6 on port 10308 2019-04-24 14:01:48.953 INFO NET: Registering server as XXXXXXXX:10308 (port is assumed to be open) 2019-04-24 14:01:48.953 INFO EDCORE: (dDispatcher)enterToState_:2 2019-04-24 14:01:48.953 ERROR Lua::Config: Call error get_server_info:?:0: attempt to index global 'mission' (a nil value). 2019-04-24 14:01:48.953 WARNING NET: Failed to get_server_info() 2019-04-24 14:01:48.953 INFO EDCORE: (dDispatcher)enterToState_:3 2019-04-24 14:01:48.953 INFO Lua: Lua CPU usage: metric: average game loading: 73.1468 % 2019-04-24 14:01:48.959 INFO EDCORE: (dDispatcher)enterToState_:4 2019-04-24 14:01:48.961 INFO NET: state=ssLoading 2019-04-24 14:01:48.970 ERROR Dispatcher: Failed to load terrain 2019-04-24 14:01:49.004 INFO NET: server has stopped 2019-04-24 14:01:49.011 INFO Config: netview stopped 2019-04-24 14:01:49.011 INFO TERRAIN: lSystem::CleanScenes() 2019-04-24 14:01:49.011 INFO VISUALIZER: StopSimulation 2019-04-24 14:01:49.011 INFO VISUALIZER: Stopped collection of statistic. Running out of ideas, so its soon back to the old ways.. at least it was working for me EDIT: My friend and i now have the same issue. It seems it doesnt read the ServerSettings.lua. It disregard any port changes within that file..
  3. Any plans on adding random presets as an option to the system? So that everytime the server start up, it gets the weather and then pick a date/time from a table of presets. Much like the fixed preset, but it chooses between all of them randomly. Instead of just real, random, fixed preset i mean. ADD: Im getting this error now, and for my own sanity im asking for some help.. https://www.dropbox.com/s/5k542ntu2goa2bw/2019-04-21%2013_10_44-Spelserver.png?dl=0 Ive been over the code to look for any kinds of error, misspelled path or whatever but cant find anything. What is the cause of that error? its working with 1.3.0 but as soon as i switch to 1.3.2 it gives the above error. Same settings in the BAT file in both instances... Ive seen this error before but cant for the love of whats holy remember what i did...
  4. Did some testing this morning, checked my settings in ME, and both Fog and Dust is unchecked. Still seeing the weird fog at the horizon. Then i checked the mission file, and around line 202 i see: ["enable_dust"] = false, ["dust_density"] = 2999, Changed the dust_density to 0: ["enable_dust"] = false, ["dust_density"] = 0, And then the weird horizon-fog disappeared. Is this just for me that this is happening? See pictures for comparison. ONLY changes between them is that the density has been set to 0 instead of 2999. Density 2999: https://www.dropbox.com/s/mg5eve1i725fxkz/TEST1.png?dl=0 Density 0 (Zero): https://www.dropbox.com/s/zr5fzmbr8zuf1hl/TEST2.png?dl=0 And looking in the script: s_sand_enable = 'false' s_sand_density_m = '0' wich is used with: s_sand_enable = '["enable_dust"] = ' s_sand_density = '["dust_density"] = ' So not really sure where the 2999 comes from...
  5. Forgot to mention im running the server on Caucasus.... :music_whistling: So that change wouldnt affect the dust option i guess? Will try it anyway.. EDIT: This is the effect im talking about: https://cdn.discordapp.com/attachments/560756151864786954/566977882409140245/2019-04-12_09_16_37-Window.png https://cdn.discordapp.com/attachments/560756151864786954/566977862398115850/2019-04-12_09_16_17-Window.png
  6. In the Mission Editor we have an option sayin "Dust Smoke Enable". Cant see that option in the METAR script. Any way to disable that weather addition? Im suspecting that its giving the server a weird results.. Weird colors and dark when it should be light. Anyway i would like to see if i can turn it off somehow? Fog_enabled is set to False at least.
  7. Great stuff! Instant download here, gonna try it tomorrow. Question, is it possible to have the program check the computer time and do a restart on a fixed time if reached? Awesome work, keep it up!
  8. You mean have a batch file kill the dcs.exe process and then start again? I rather not do that since im running two servers so killing dcs.exe would kill them both. And i dont know of any way for scripting to know the computers real time so it could warn the players for an upcoming restart if they were to be synced to the computer clock.
  9. Any of you guys that runs METAR run it with some kind of automation? eg the server restarts every 6 hours and picks new weather info and new time? I have a scheduled reboot on the computer at 0500 every morning and then the mission restarts every 6 hours. Thinking on how i could incorporate the METAR system into that in a clever way. One way, is to have it be started every morning at 0500, then that weather info will stay all day along with real time... Any ideas?
  10. Yea after some trial and error i found it. Changed: start /D%DCS_PATH% /B dcs.exe into: start /D%DCS_PATH% /B dcs.exe --server --norender And it worked! Follow up question. The time is now working as intended, sort of. Havent been able to test if it chooses the random times, will do that tonight after 1800. But the date. When selecting REAL time, is it possible to skip the date then? So i can pick wich date i want to play on, but the time is real?
  11. Anybody running this with the "dedicated server" settings since after last patch?
  12. Check out: https://forums.eagle.ru/showthread.php?p=3098216 With this you can block certain slots with certain conditions. Some scripting required. We use it to block the usage of slots from airports that arent controlled by friendly forces. And also have other conditions for unlocking them, doesnt have to be connected to the ownship of the airport. Hope that helps
  13. I just started looking into this. Got it working after some troubleshooting. I have random time on, but always keep getting the dark hours of the day. Found that this might help: But dont know when it will kick in. I see that there is a table in dcs_weather in wich it got "template" times. But it doesnt seem to use those?
  14. Hello, As the subject says, we cannot select any weapons when starting cold on the ground at Al Dhafra. Right clicking each category shows empty. We can only use the preset loadouts. Ive tested it with a cold start A-10C on the same airfield and that worked. Any suggestions what this might be caused by? EDIT: It seems that the slots with numbers above 200 doesnt work. Moved the aircraft to the 130 area and then it worked.
×
×
  • Create New...