Jump to content

Recommended Posts

Posted (edited)

Hi, I need help with Mig 19. I bought game last week, and when I set control settings, my settings work only in training missions. In other missions like campaign the control settings is missing, and default setting from game dont work neither

:helpsmilie::helpsmilie::helpsmilie::helpsmilie:r.

Edited by BIGNEWY
  • Replies 466
  • Created
  • Last Reply

Top Posters In This Topic

  • ED Team
Posted

Hi welcome to the forum

 

Please ensure you are not using game avionics

 

they have a different controls set and some missions are not made for game mode

 

 

smallCATPILOT.PNG.04bbece1b27ff1b2c193b174ec410fc0.PNG

Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status

Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal

Posted

Thanks, Problem is that i have simulation mode set on and control dont respond. Now I install drivers for thrustmster 16000. And no progress. when I reinstall DCS world, will I bought mig 19 modul again? or not?

Posted

Hi there, There are two different controller profiles, one being Mig19 game and the other Mig19 Sim ( from memory). Make sure that if you have settings set up for simulation mode that you edit the Mig 19 SIM profile.

 

Assuming you reinstall and login with the same user account details then your module will still be there for you.

Posted
A few changes were made to the cockpit and a few problems that could be the cause of the lower performance in VR were found and fixed. So far in testing the FPS improved and the fix should be available in the next update for you to test.

 

One thing is important to notice however. When the dynamic radar ground return is active this could cause a drop in FPS as this representation is kind of resource heavy.

 

 

 

@Overstratos, Was this fix released?

 

Thanks

Posted

I know about 2 settings profiles, I tryed both. when I make the changings in game profil, is everything OK, but when I make changings in sim profil, the game dont response, it look like I set nothing. Interesting is, that when I play training missions it is OK, but in other campainges or fast battle it dont work correctly.

  • ED Team
Posted

Hi

 

please take a look at my signature and the crash advice.

 

It may rule out a settings issue, and we can also check your build is functioning ok.

 

I have tested and all seems ok on my end.

 

Also please find images below that may help

Screen_191013_204134.thumb.jpg.558cdef44baa3c4e4d54d578fda40048.jpg

Screen_191013_204057.thumb.jpg.7719d681961f62652f2b55b91e424bfc.jpg

Screen_191013_204122.thumb.jpg.401bb13f4c1f39f6203e558a9b0f7609.jpg

smallCATPILOT.PNG.04bbece1b27ff1b2c193b174ec410fc0.PNG

Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status

Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal

Posted

The manual for the MiG-19 claims that the engine start button must be held for a few seconds in order to begin the start sequence, but in-game a quick click will suffice. Additionally, if the start button is pressed and then the throttle is moved to idle (rather than the other way around), the engine will still begin to start.

 

Also, if I right-click to move the pressurization lever to the 'open' position, and then right-click it again to close it, it will make the movement noise but still stick in the 'open' position.

Posted (edited)

Just bought the module. Get these stutters when rolling/pitching. I don't think it's fps related because even with pixel density 1.0, very low settings, and locked 40 fps ASW forced, I still get the stutters. No other module does this for me. I don't say this lightly but this honestly makes it unplayable :(

 

edit: nevermind. should have used oculus tray tool from the start. seems I am constantly dipping just below 40 fps which is probably causing the stuttering.

Edited by JoeyJoJoJunior

i7 6700k @ 4.6, Gigabyte Z170X-UD3, 32GB DDR4 2666, GTX 1070, Rift S | MS Sidewinder FFB2 w/ TM F-22 Pro Grip, TM TWCS Throttle, VKB T-Rudder Mk. IV

Posted

Thanks for the info, I also noticed the stuttering recently.

Hardware: VPForce Rhino, FSSB R3 Ultra, Virpil WarBRD, Hotas Warthog, Winwing F15EX, Slaw Rudder, GVL224 Trio Throttle, Thrustmaster MFDs, Saitek Trim wheel, Trackir 5, Quest Pro

Posted

Hey OverStratos thanks for the update, hopefully we can get it on the next OB release? Curious to know what else you have coming for the Farmer? Pilot model?

 

Cheers

Posted
All the issues that remain in the MiG-19 will be fixed and also some new features will also be added. These includes more tunning to the FM for an even more realistic ITR and STR behavior, better engine simulation, dedicated sounds and many more. Currently all the coding force is focusing on the modules that arrived before the MiG-19P, so as soon as they are available work will continue on it.

 

 

Ahhh... just found this, never mind mate!

Posted

Not sure if this was a one off or not but i just had an engine and a wing shot to bits, ejected and (apart from the view remaining centred on the now vacant Mig19?) the plane started to spiral in a way not physically possible which almost resembled elastic banding online but this was offline messing about in the ME. 4 Mig19 vs 4 Mig15 dogfight. It was the weirdest thing ever and i wish i could show you a clip of it.

May be worth checking out the damage model on the Mig just to make sure there isnt anything radically out of place which might cause this?

 

:)

Posted

There was a problem with the coordinates for pilot ejection. This was fixed now and it´s waiting for the next update. Not sure if that is creating the issue, we will test to see.

Posted

+1 on this one. I was flying on the Persian Gulf map and tried playing around with the brightness knob and day/night switch, but could almost not make out anything on the radar screen.

  • 2 weeks later...
Posted

Pop over a track file if you can and I have a go on my machine with your file.

 

I have tried to replicate but I cant on the latest version.



 

Water cooled i9-9900K | Maximus Code XI MB | RTX3090  | 64GB | HP Reverb G2 
Posted
I'm definitely not the only one experiencing this. Someone else showed it to me in multiplayer.

 

 

 

Here's a track.

Thank you

 

Sent from my SM-G960F using Tapatalk



 

Water cooled i9-9900K | Maximus Code XI MB | RTX3090  | 64GB | HP Reverb G2 
Posted

Yes the same sort of thing except mine was in flight so the motion was vastly exaggerated. Very strange. The camera remained on the aircraft after eject, pilot and chute was nowhere to be seen

Posted

yes, it was included but forgot to add it in the changelog, sorry.

 

- New cockpit and external model with VR improvements

- Fixed seated pilot being ejected 500 meters away from the cockpit

Posted (edited)

Hello,

 

tried out the MiG-19 after the latest move to stable release.

DCS/2.5.5.39384 UTC 2019-11-17 13:46:23

 

I was unable to contact ATC. I set channels two and six to 133 MHz in mission editor and wanted to contact Kobuleti. I couldn't get this to work.

 

Can someone check attached trackfile if I'm doing something wrong? I tried different switch positions but to no luck.

 

Thanks

Jens

Edited by gulredrel
Posted (edited)
I was unable to contact ATC. I set channels two and six to 133 MHz in mission editor and wanted to contact Kobuleti. I couldn't get this to work.

 

Can someone check attached trackfile if I'm doing something wrong? I tried different switch positions but to no luck.

 

Looking at your mission/track file, you have Ch 3 and Ch 6 setup for Kobuleti (133 MHz).

 

Checking the kneeboard "MiG-19 Radio" page, it seems only Ch 3 loaded with the correct frequency (bug ?).

 

• Battery ON

• Radio ON

• Ch 3 select

Radio Volume Up

• # key - com menu

 

... was all I needed to contact ATC for permission to startup.

 

I watched your track, but it was hard to tell which keys/channels you were using.

 

Sydy's Checklist may be helpful if you don't already have it

 

https://www.digitalcombatsimulator.com/en/files/3303784/

 

Tested in DCS 2.5.5.39384

Edited by Ramsay
Add Volume Up

i9 9900K @4.8GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 11 Pro x64, Odyssey G93SC 5120X1440

  • Recently Browsing   0 members

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