Jump to content

Latest update trouble... again


Recommended Posts

I think it asks if you wish to update when opening DCS . You can also revert to a previous build , or convert to stable or OB . Think there is a hotfix coming monday , if you can wait for that , maybe a fix .

9700k @ stock , Aorus Pro Z390 wifi , 32gb 3200 mhz CL16 , 1tb EVO 970 , MSI RX 6800XT Gaming X TRIO , Seasonic Prime 850w Gold , Coolermaster H500m , Noctua NH-D15S , CH Pro throttle and T50CM2/WarBrD base on Foxxmounts , CH pedals , Reverb G2v2

Link to comment
Share on other sites

I use a thrustmaster. The latest update seems to have disabled the rudder action on my stick.

 

 

I start to cringe every time DCS updates... Any way we can disable them?

 

 

Make sure the rudder isn't assigned to other USB devices as well. This is pretty common and the conflict leads to all kinds of problems.

 

 

 

I'm assuming in Windows' Control Panel, Joystick, you can still see your rudder movement?

hsb

HW Spec in Spoiler

---

 

i7-10700K Direct-To-Die/OC'ed to 5.1GHz, MSI Z490 MB, 32GB DDR4 3200MHz, EVGA 2080 Ti FTW3, NVMe+SSD, Win 10 x64 Pro, MFG, Warthog, TM MFDs, Komodo Huey set, Rverbe G1

 

Link to comment
Share on other sites

I use a thrustmaster. The latest update seems to have disabled the rudder action on my stick.

 

 

I start to cringe every time DCS updates... Any way we can disable them?

 

Uninstall your openbeta versjon. Install the release version and only play with that one. Much better for you.

Link to comment
Share on other sites

Thanks for the responses. I will pay closer attention next time and deny updating or just stick to the Alpha release. Also, Windows is reading my rudder movement, I did not know I could check for that so thanks...

 

 

For now I will reinstall DCS World...

 

 

There's a repair option as well. You don't have to uninstall and reinstall it.

 

 

You can do it from the command line or install this utility.

 

 

 

https://forums.eagle.ru/showthread.php?t=160053

hsb

HW Spec in Spoiler

---

 

i7-10700K Direct-To-Die/OC'ed to 5.1GHz, MSI Z490 MB, 32GB DDR4 3200MHz, EVGA 2080 Ti FTW3, NVMe+SSD, Win 10 x64 Pro, MFG, Warthog, TM MFDs, Komodo Huey set, Rverbe G1

 

Link to comment
Share on other sites

  • ED Team

This update was meant to disable the canned profiles so your Saved Games profiles should work now, if you did any modding to make it work before the hotfix, like deleting profiles or replacing them, it could cause some issues.

64Sig.png
Forum RulesMy YouTube • My Discord - NineLine#0440• **How to Report a Bug**

1146563203_makefg(6).png.82dab0a01be3a361522f3fff75916ba4.png  80141746_makefg(1).png.6fa028f2fe35222644e87c786da1fabb.png  28661714_makefg(2).png.b3816386a8f83b0cceab6cb43ae2477e.png  389390805_makefg(3).png.bca83a238dd2aaf235ea3ce2873b55bc.png  216757889_makefg(4).png.35cb826069cdae5c1a164a94deaff377.png  1359338181_makefg(5).png.e6135dea01fa097e5d841ee5fb3c2dc5.png

Link to comment
Share on other sites

new update made it worse

 

I had my profiles set and working yesterday there was and up date today and now i cant change my axses controls nor erase the ones default one causing duel bindings yet again

Screen_181016_224853.thumb.png.6ece1843739132adc23bc0611b1f1277.png

[sIGPIC][/sIGPIC]

Window 10, i9-9900,2080TI, 32GB ram Puma Pro Flight Trainer, 2 x 1TB WB SSD NVMe HP Reverb

Link to comment
Share on other sites

I understand progress is painful but come on guys...Spent an hour after the last update having to read through posts on how to figure out the problem and redo all controller settings.

 

This update the same issue again? In axis commands getting red boxes again for pitch and roll, so I have to delete profile, repair and do this all over again????

 

It would be nice if a warning could be added to the change log that this could happen. I update just to keep the latest but this could have waited so I dont have to spend half of my 2 free hours fixing what I already fixed before...

Intel i9-13900k, Asus Z790-E Gaming Wifi II mobo, 64gb Corsair DDR5-6400 RGB ram 2x32gb XMP2 profile, 2TB Crucial T700 PCIE 5.0 SSD internal, 2TB Samsung 980 Pro PCIE 4.0 SSD internal, Asus Tuf Gaming overclocked Nvidia RTX 4090, Corsair 7000X Case with 5 x 120mm intake fans and 4 x 140mm exhaust fans, side mounted Corsair H150i Elite Capellix 360mm liquid cooler w/Elite LCD with 6 x 120mm fans in push-pull intake configuration 2 x 32" Asus 2560x1440 displays, TrackIR5 w/pro clip, Thrustmaster Warthog stick and throttle, CH Fighterstick Pro and Pebble Beach Velocity pedals. 

Link to comment
Share on other sites

More of a warning would have been nice for the previous patch, but this is Open Beta, it's not always stable, and this is why we run these updates through Open Beta.

More of a warning? I haven't seen any warning!

 

When such new, potentially disruptive, functionality is introduced the user community is entitled to get information about what it is, what it does, and how to handle any issues. There was nothing - except a basd surprise!

 

And in the world of professional software management, a beta version is a fairly stable version for testing by educated and well-informed users before the general release. It is not a place for trying poorly conceived and insufficiently alpha-tested functionality.

ED uses the Open Beta to market new modules that are not ready for general release. That approach provides cash flow from products that are still in development and that helps to finance development, great for ED, and it provides a lot of feedback that's beneficial for the development process. But it also attracts far more users into he beta version than you would allow for a "normal" beta release, And these many users need a higher level of quality and better communication than what we have seen recently.


Edited by LeCuvier

LeCuvier

Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5

Link to comment
Share on other sites

  • ED Team
More of a warning? I haven't seen any warning!

 

 

Open Beta should be considered a warning in name, you should expect to see issues like this, you shouldn't mod your install, you should report any issues you have, its a test environment, I know its made worse by some of the top servers running Open Beta, but it doesn't change the fact that this is a testing version and should be treated as such, and to expect hiccups like this.

 

Open Beta goes through struggles in the hopes we don't pass those struggles to Stable.

64Sig.png
Forum RulesMy YouTube • My Discord - NineLine#0440• **How to Report a Bug**

1146563203_makefg(6).png.82dab0a01be3a361522f3fff75916ba4.png  80141746_makefg(1).png.6fa028f2fe35222644e87c786da1fabb.png  28661714_makefg(2).png.b3816386a8f83b0cceab6cb43ae2477e.png  389390805_makefg(3).png.bca83a238dd2aaf235ea3ce2873b55bc.png  216757889_makefg(4).png.35cb826069cdae5c1a164a94deaff377.png  1359338181_makefg(5).png.e6135dea01fa097e5d841ee5fb3c2dc5.png

Link to comment
Share on other sites

@NineLine: your statement suggests that we should not expect improvement.

I will therefore heed the "warning in name" and stay out of OB, except for flying the F/A-18 when there is new functionality.

LeCuvier

Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5

Link to comment
Share on other sites

  • ED Team
@NineLine: your statement suggests that we should not expect improvement.

I will therefore heed the "warning in name" and stay out of OB, except for flying the F/A-18 when there is new functionality.

 

It's not really about improvement, ED is a smallish development studio, and the sim is growing in leaps and bounds, Open Beta is offered for a wider testing sample in order to keep these issues out of Stable as much as possible.

 

That said, its not for everyone, so in some cases, it is best to avoid Open Beta. You have to be ok with testing, troubleshooting and reporting issues.

64Sig.png
Forum RulesMy YouTube • My Discord - NineLine#0440• **How to Report a Bug**

1146563203_makefg(6).png.82dab0a01be3a361522f3fff75916ba4.png  80141746_makefg(1).png.6fa028f2fe35222644e87c786da1fabb.png  28661714_makefg(2).png.b3816386a8f83b0cceab6cb43ae2477e.png  389390805_makefg(3).png.bca83a238dd2aaf235ea3ce2873b55bc.png  216757889_makefg(4).png.35cb826069cdae5c1a164a94deaff377.png  1359338181_makefg(5).png.e6135dea01fa097e5d841ee5fb3c2dc5.png

Link to comment
Share on other sites

Flippin'Ek. After My binds were fixed yesterday, (I posted in this thread to say Hooray.. now working) . Today first time I ran DCS F18 they were TRASHED again. Hadn't touched anything since I flew yesterday. So I loaded the previously saved good profile that worked yesterday from the controls screen and again NO EFFECT, still trashed. Seems that DCS is randomly loading/not loading controller profiles / randomly trashing profiles EVEN though there has been no update since it last worked ok. I fear I am going to have to ABANDON the DCS F18 for some weeks to allow (hopefully) things to get sorted out, I simply haven't got the time to manually reset all my binds every day, and without working binds its is UNFLYABLE. Extra info.

 

EXTRA INFO

I notice that TODAY when the problem re-occurred that the ORDER the devices appear in the columns on the Controls screen has changed,

Yesterday the order was

KEYBOARD

THROTTLE THRUSRMASTER WARTHOG

JOYSTICK THRUSTMASTER WARTHOG

RUDDER (hex device address)

MOUSE

 

Today the order of the columns has changed on the controls screen to

KEYBOARD

JOYSTICK THRUSTMASTER WARTHOG

THROTTLE THRUSRMASTER WARTHOG

RUDDER (hex device address)

MOUSE

 

and many of the bindings from yesterday, which worked, have vanished/are wrong today.

No devices were replugged (for the Thrustmaster setup each controller is a distinct USB device), but the PC was rebooted overnight.

Could it be that DCS is mapping actual windows devices to 'controller roles' in the bindings based on the device ADDRESS (which of course can vary with every boot, windows loves indirection) rather than to the device NAME in Windows?

 

I have also noticed that the OPEN BETA and the RELEASE version of DCS show the devices in a different column order on the controls screen


Edited by Silversmith
Link to comment
Share on other sites

  • ED Team

Had you changed anything within the actual install folders, such as copy profiles to the actual DCS install instead of Saved Games? Might be worth running a repair on your Open Beta, I am not hearing anyone else having this issue to my knowledge.

 

 

Flippin'Ek. After My binds were fixed yesterday, (I posted in this thread to say Hooray.. now working) . Today first time I ran DCS F18 they were TRASHED again. Hadn't touched anything since I flew yesterday. So I loaded the previously saved good profile that worked yesterday from the controls screen and again NO EFFECT, still trashed. Seems that DCS is randomly loading/not loading controller profiles / randomly trashing profiles EVEN though there has been no update since it last worked ok. I fear I am going to have to ABANDON the DCS F18 for some weeks to allow (hopefully) things to get sorted out, I simply haven't got the time to manually reset all my binds every day, and without working binds its is UNFLYABLE. Extra info.

 

EXTRA INFO

I notice that TODAY when the problem re-occurred that the ORDER the devices appear in the columns on the Controls screen has changed,

Yesterday the order was

KEYBOARD

THROTTLE THRUSRMASTER WARTHOG

JOYSTICK THRUSTMASTER WARTHOG

RUDDER (hex device address)

MOUSE

 

Today the order of the columns has changed on the controls screen to

KEYBOARD

JOYSTICK THRUSTMASTER WARTHOG

THROTTLE THRUSRMASTER WARTHOG

RUDDER (hex device address)

MOUSE

 

and many of the bindings from yesterday, which worked, have vanished/are wrong today.

No devices were replugged (for the Thrustmaster setup each controller is a distinct USB device), but the PC was rebooted overnight.

Could it be that DCS is mapping actual windows devices to 'controller roles' in the bindings based on the device ADDRESS (which of course can vary with every boot, windows loves indirection) rather than to the device NAME in Windows?

 

I have also noticed that the OPEN BETA and the RELEASE version of DCS show the devices in a different column order on the controls screen

64Sig.png
Forum RulesMy YouTube • My Discord - NineLine#0440• **How to Report a Bug**

1146563203_makefg(6).png.82dab0a01be3a361522f3fff75916ba4.png  80141746_makefg(1).png.6fa028f2fe35222644e87c786da1fabb.png  28661714_makefg(2).png.b3816386a8f83b0cceab6cb43ae2477e.png  389390805_makefg(3).png.bca83a238dd2aaf235ea3ce2873b55bc.png  216757889_makefg(4).png.35cb826069cdae5c1a164a94deaff377.png  1359338181_makefg(5).png.e6135dea01fa097e5d841ee5fb3c2dc5.png

Link to comment
Share on other sites

Had you changed anything within the actual install folders, such as copy profiles to the actual DCS install instead of Saved Games? Might be worth running a repair on your Open Beta, I am not hearing anyone else having this issue to my knowledge.

 

No not fooled around with anything, but happy to try a repair. Lets see how it goes

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...