跳转到帖子

philstyle

Members
  • 帖子数

    1,882
  • 注册日期

  • 上次访问

最新回复 发布由 philstyle

  1. 19 hours ago, Baldrick33 said:

    In my experience DCS needs to be running for it to show up in the list.

    Quadviews does the fixed foveated rendering for the G2 though I could not get it to work with the Oasis driver, the mission would hang on startup. Only tried it briefly, not sure if it is a known issue? Disabling it fixed it.


    OK, thanks.
    I asked on the reddit subs and all I got was downvotes. Glad there's help here. 
    Not sure why I even expected to get any help from that lot. 

  2. I have two questions. Am using a reverb G2, windows 11.

    1. As per the uploaded screenshot. DCS itself does not show in the list of applications under video>per application settings. Do I need to add DCS somehow to this list, or do I use one of those existing apps to set the settings which will apply to DCS?

    2. Is there a way to enable a foveated-type rendering now, similar to what we could do with openXR toolkit?

     

    null

    image.jpeg

  3. On 9/10/2025 at 2:19 AM, Cab said:

    The next time I restart my headset and SteamVR, I consistently get the message below about my GPU having trouble communicating with my headset. After uninstalling/reinstalling Steam/SteamVR/Oasis, it works again. This has happened every time without fail.

     

     

     

    I have similar issue, but switching to 60 fps and then back again to 90 fps seems to fix it for me..

     

    • Thanks 1
  4. With compostie version 0.6.3 the whole installation and use process for this appears to have changed. (https://gitlab.com/Jabbah/open-composite-acc/-/releases)


    Does anyone have a link to an updated "how to" guide since the move to 0.6.3, which steps me though each download and install?

    I have looked at a few YT videos that are as recent as March 2022, and they all seem to be referring to the older 0.6.2 layout, the links for which are no longer usable...

  5. This image shows what happens to the weapons availability at an airfield every time ED puts out a new patch with changes to the weapons.

    1. Updated weapons default back to 100 availability, ruining any attempt by mission makers and hosts to stick to custom weapons sets (especially important for creating historically-based limitations)
    2. New weapons get added which populate the top of the list. These remain un-named until we do a bit of jiggery pokery to effectively reset the whole warehousing at that base, which requires a couple of mission saves and re-loads.

    Now, this isn't a problem for people who host missions with 1 or 2 bases or people who don't care about weapons availability. But for those of us who do or did, this can require 30+ minutes per mission to "fix" per patch (each airfield having to be checked and updated). I've hosted playlists of 15 to 20 missions before, meaning that a single patch resulted in the loss of 8 hours of my time to go through and correct all this induced drag.

    A the risk of being accused of being poisonous some more, this is a massive disincentive to hosting complex and sophisticated missions. I know I am not the first to give up due to this (and other) aspect that put time barriers in the way of sophisticated mission design and push us all back in the direction of banal/ same-same copy-cat missions.

     

    image.png

    Thread locked.

    • Like 7
    • Thanks 2
  6. Interstingly, I have just noticed that my vey first post on the ED forums, when I was considering getting invovled in running MP in DCS, was to probe this very concenpt. Grimes was one of the few people who responded then, too. . .  Such a shame that 5 years later we are still asking the same unanswered questions. 
     



     

  7. 14 hours ago, gordonvembu said:

    cool, i appreciate your non defensive reply.

    i am just dipping my toes into dcs eventhough i have been here since

    lockon, flamming cliffs 1/2/3.

    ww2 air combat is my fav genre.

    ergo, i want it done well and be a passion not a job for devs.

    that said...if you are gonna setup a server for full historical accuracy,

    you can not have the unholy trinity enabled.

    they are gps, auto rudder n takeoff assistance.

    now all i am asking philstlye aka god is what is the status on these 3.

    i luv his obsession with ww2 warbirds but phil you must stop those 3 existing...hmmm, also xnay the zoom...


    As you already know from my reply to the exact same question on my YoutTube channel, all of the three things you identify in your rhetorical "unholy trinity" are NOT available to server administrators to turn on or off. They exist client-side. If you wish for them to be made availalbe as server options then you need to lobby Eagle Dynamics, who make the software, not SoW who simply use it. The DCS wishlist forum is here:https://forums.eagle.ru/forum/207-dcs-wishlist/
    That would be the place to express your wish for those aspects of DCS to be within the control of the server host.

    That sums up the status of these three things as far as SoW is concerned. .

  8. 1 hour ago, OLD CROW said:

    IT ONLY SHOWED A REPETITIVE MISBEHAVIOR OLDER THAN PYRIMAMIDS. AND YES, IMAO, I REPEAT MISBEHAVIOR WHILE SOME OTHERS SEE A NOOB.

    Case Closed. AMEN

     

     


    As admin and owner of the server and OP for this thread, and therefore "god" with respect to it, I declare that no "misbehaviour" occurred. It was simple pilot error.
    Just to be absolutely clear in case anyone is confused: There is no rule against this on the server. It is NOT considered in any way worth reporting or making a complaint about.

    NOW, the case is closed. My will be done.

    • Like 5
  9. Clarification of server rules and warnings related to player disconnections:
    https://stormofwar.net/2021/12/20/december-2021-disconnecting/

    Deliberately disconnecting from the server while in control of a moving aircraft is prohibited on the Storm of War server. Pilots must come to a complete stop or bailout first. This applies on the ground as well as in the air. Players who disconnect in the manner described above will be warned on the stats pages. Repeated disconnects after a warning might result in being banned from the server.
    (Changing roles whilst similarly airborne is also not permitted, but this is restricted by server-side scripting)

    • Like 3
  10. On 12/18/2021 at 2:04 PM, drmorrish said:

    It may have been talked about ad nauseam, it may not be historically accurate but you can bet it’s limiting player base……I’m just getting into DCS Warbirds, no interest in SOW because of the MW50 thing. We want COMPETITIVE gameplay. Not a re enactment of a lost war. Boom and Zoom planes without the zoom are boring. Just my .02. I lose to plenty of spits and mustangs on other servers without such limitations. 


    SoW is definitely not for you.
    I suggest you keep playing on the other excellent WW2 servers.

    • Like 2
  11. Mission updates V110 and V111 being moved over to the server now:

    v111 – December 2021
    v110 – December 2021
    • Fixed airspeeds of some A20 raids so that they stay together
    • AI interceptors adjusted
    • Added new AI bomber raid system which allows for randomization of raid spawns
    • Added new tracking for AI bomber raids so that escort duties can be recognized in he stats
    • streamlined all administrative triggers in missions
    • Like 1
    • Thanks 2
  12. SERVER ANNOUNCEMENT:

    Storm of War has now implemented the following into the mission set (version 110 missions) on the server:
    1. AI Bomber raids for both teams will no longer spawn at predictable times during the mission, they will randomize, (within limits) each time a mission runs
    2. The spawn time for the bombers is no longer contained within the miz file itself. It will no longer be possible to open up a trk or miz file and check when the bombers are to spawn in
    3. We are now recording exactly how many bombers from each raid make it "home". This will mean, soon (hopefully) that we can also collect information about who was responsible for ensuring that a raid made it back. Escorting and protecting bomber formations will, therefore, soon be something we can show in the stats and award campaign ribbons for.

    Big thanks to 2./JG54 Teckel for writing most of the code for this, and the SoW Projects Team for all the testing

    • Like 4
    • Thanks 1
  13. I have noticed this also. The Allied heavy AA (the British 2.7 QF) is unable to see targets unless they are extremely close by (under 1500m range it seems). There is now a massive disparity in heavy flak behavior between allied and axis heavy flak guns in the WW2 assets.
     

    trk file which demonstrates the ineffective guns:

    https://drive.google.com/file/d/1RsYm5Y9hMdT58rHPC3dAxMfU1NFespS3/view?usp=sharing

    • Like 2
  14. 12 hours ago, FF*Mamba said:

    i see.that people watched my videos, and half of the people started flying with a hidden tape - it shows that people are learning to fly on my videos. I'm sorry, if something is not clear, then this is google translator)

     

    Hey Mamba, use deepl to translate, it is much better.
    Используйте Deepl для перевода, он намного лучше.

    https://www.deepl.com/translator

    • Thanks 1
  15. Player/ pilot ribbons for November have been awarded. The full investiture and list of recipients is now up on the SoW website here:
    https://stormofwar.net/2021/12/02/december-2021-sow-ribbons-investiture-for-november-2021/

    There were 33 ribbons awarded this month in each category, another very busy month on the server. Just under 1500 unique players logged flight time, with over 220 flying 10+ hours in the month.

    Congratulations to all awarded pilots.

    • Thanks 1
  16. Some ships (not clear if it is the WW2 asset ships) are causing large numbers of ERRORS to be writen to the DCS Log.
    See the relevant WARNINGs and ERRORs below

     

    2021-11-29 15:15:13.639 INFO    APP: MissionSpawn:spawnShips 4
    2021-11-29 15:15:13.639 ERROR   Lua::Config: Call error Sounder_create:?:0: attempt to index a nil value.
    2021-11-29 15:15:13.642 WARNING EFFECTS2: OParticleSystem: preset '' not found in 'shipTrail.lua', using default
    2021-11-29 15:15:13.643 ERROR   EFFECTS: ODCSParticleSystem: trying to set parameter for emitter that doesn't exists in shipTrail.lua
    2021-11-29 15:15:13.643 ERROR   Lua::Config: Call error Sounder_create:?:0: attempt to index a nil value.
    2021-11-29 15:15:13.645 WARNING LOG: 2 duplicate message(s) skipped.
    2021-11-29 15:15:13.645 WARNING EFFECTS2: OParticleSystem: preset '' not found in 'shipTrail.lua', using default
    2021-11-29 15:15:13.645 ERROR   EFFECTS: ODCSParticleSystem: trying to set parameter for emitter that doesn't exists in shipTrail.lua
    2021-11-29 15:15:13.645 WARNING EFFECTS2: OParticleSystem: preset '' not found in 'shipTrail.lua', using default
    2021-11-29 15:15:13.645 ERROR   EFFECTS: ODCSParticleSystem: trying to set parameter for emitter that doesn't exists in shipTrail.lua
    2021-11-29 15:15:13.645 WARNING EFFECTS2: OParticleSystem: preset '' not found in 'shipTrail.lua', using default
    2021-11-29 15:15:13.646 ERROR   EFFECTS: ODCSParticleSystem: trying to set parameter for emitter that doesn't exists in shipTrail.lua
    2021-11-29 15:15:13.646 ERROR   Lua::Config: Call error Sounder_create:?:0: attempt to index a nil value.
    2021-11-29 15:15:13.647 WARNING LOG: 1 duplicate message(s) skipped.
    2021-11-29 15:15:13.647 WARNING EFFECTS2: OParticleSystem: preset '' not found in 'shipTrail.lua', using default
    2021-11-29 15:15:13.648 ERROR   EFFECTS: ODCSParticleSystem: trying to set parameter for emitter that doesn't exists in shipTrail.lua
    2021-11-29 15:15:13.648 WARNING EFFECTS2: OParticleSystem: preset '' not found in 'shipTrail.lua', using default
    2021-11-29 15:15:13.648 ERROR   EFFECTS: ODCSParticleSystem: trying to set parameter for emitter that doesn't exists in shipTrail.lua
    2021-11-29 15:15:13.648 ERROR   Lua::Config: Call error Sounder_create:?:0: attempt to index a nil value.
    2021-11-29 15:15:13.649 WARNING EFFECTS2: OParticleSystem: preset '' not found in 'shipTrail.lua', using default
    2021-11-29 15:15:13.649 ERROR   EFFECTS: ODCSParticleSystem: trying to set parameter for emitter that doesn't exists in shipTrail.lua
    2021-11-29 15:15:13.649 ERROR   Lua::Config: Call error Sounder_create:?:0: attempt to index a nil value.
    2021-11-29 15:15:13.649 WARNING EFFECTS2: OParticleSystem: preset '' not found in 'shipTrail.lua', using default
    2021-11-29 15:15:13.650 ERROR   EFFECTS: ODCSParticleSystem: trying to set parameter for emitter that doesn't exists in shipTrail.lua
    2021-11-29 15:15:13.650 INFO    APP: MissionSpawn:spawnShips 2

     

    • Like 8
    • Thanks 2
  17. As per the title, the DCS WW2 assets pack Puma unit is causing ERRORS which are recorded in the DCS LOG as per below:

    2021-11-29 15:10:21.800 ERROR   wWeaponSystem: invalid connector CENTER_TOWER for unit Sd_Kfz_234_2_Puma
    2021-11-29 15:10:21.927 WARNING LOG: 1 duplicate message(s) skipped.
    2021-11-29 15:10:22.033 ERROR   wWeaponSystem: invalid connector CENTER_TOWER for unit Sd_Kfz_234_2_Puma
    2021-11-29 15:10:22.172 WARNING LOG: 2 duplicate message(s) skipped.

     

    • Like 6
    • Thanks 2
  18. The V-1 Ramp unit, as showing in the image attached is producing these errors in the DCS log during mission loading sequences:
     

    2021-11-29 15:10:21.927 ERROR   cLauncherMissile: distanceMax is invalid for LN[1], WS[1], host RT3 V1-Site
    2021-11-29 15:10:21.927 ERROR   cLauncherMissile: distanceMax is invalid for LN[1], WS[1], host RT3 V1-1

     

    unknown.png

    • Like 6
    • Thanks 2
×
×
  • 创建新的...