annoluce

Thanks a lot!

Hi guys, back in the past I used a very well made high res cockpit (Ricardo's). Now it says that it's incompatible with the 2.7 release. Is there a compatible version of high resolution cockpit for BS2? Thanks

Hi guys, it just happened to me... I was modifying the UI layer and it magically wiped out all my throttle x56 assignments... Or better said it assigned totally arbitrary mappings... How come? I have most recent update. Thanks

As others have pointed out, the problem is the deferred shading. Once disabled everything is back to the norm, aside that all the shadings for trees and world look terrible. Trees in particular seem plastic maiden, everything just looks Battlezone 80 if you now what I mean. Hopefully ed will fix this and give us back both the lighting and the deferred shading!

Guys, I think there is a misunderstanding here, as I see many people pointing out that instruments lights are not working with Ka50 in 2.5. Gauges light not working is the consequence, not the cause. It appears that the shaders/lighting of the sim are completely wrong in the Ka50. Don't know about other modules. As I posted in another thread: Yesterday we did a multiplayer flight using 2.5 and Ka-50. No one of my flight mates was able to see nothing in the cockpit. The mission was at night, when the daylight came it got slightly better (even though the shading was not correct at all) but during the night I was not able to distinguish the single switches, all was pitch black also using cockpit light and I wasn't able to ramp start. Now I don't think it is a problem of instrument lighting as some reported. It is a problem of cockpit lighting/shading, at higher /general video shading level, how to say. All seems to be ugly, over-contrasted, such as if the curves and the black point of the shading was completely mistaken, and the sensation was to have a layer of haze in the cockpit, something I saw only when applying SweetFX shaders to a game and doing it completely wrong. Will this be fixed? I hope so, because in the 1.5 the Ka50 using Ricardo texture was a piece of beauty. I use Oculus and the cockpit lighting/shading is one of the reasons to go VR and use it with DCS, to start with. Somone is experiencing the same? Hopefully ED is working on this otherwise I would say the Ka50 is unplayable.

I will then repeat my considerations there.

What is the thread you are referring to? I see a few threads about this issue, but all the threads are misleadingly describing a problem with instrument lights, which is NOT the issue. The cockpit shading is completely wrong, and this issue is independent from the intruments lights. Instruments not being visible is the consequence of having a bad shading/lighting, not the cause.

Pilots, Yesterday we did a multiplayer flight using 2.5 and Ka-50. No one of my flight mates was able to see nothing in the cockpit. The mission was at night, when the daylight came it got slightly better but during the night I was not able to distinguish the single switches, all was pitch black also using cockpit light and I wasn't able to ramp start. Now I don't think it is a problem of instrument lighting as some reported. It is a problem of cockpit lighting/shading, at higher /general video shading level, how to say. All seems to be ugly, over-contrasted, such as if the curves and the black point of the shading was completely mistaken, and the sensation was to have a layer of haze in the cockpit, something I saw only when applying SweetFX shaders to a game and doing it completely wrong. Will this be fixed? I hope so, because in the 1.5 the Ka50 using Ricardo texture was a piece of beauty. I use Oculus and the cockpit lighting/shading is one of the reasons to go VR and use it with DCS, to start with. Somone is experiencing the same? Hopefully ED is working on this otherwise I would say the Ka50 is unplayable. Cheers Max

Brixmis, you are right and it is extremely frustrating each time I start windows to go and set up again the axis inversion. I should try some other trick such as hard reset of calibration, not yet done. I have now another problem, which is that the key programming only works with the stick, it won't work anymore with the throttle. It used to work at beginning with the throttle as well, which makes me think that something spoiled the throttle settings/drivers, but I can't figure out what. It is a pity since the hotas quality and feeling is very nice, very smooth throttle movement and I'm very happy with the button variety... But really frustrated by the software and drivers. I have also the G25 Logitech wheel and it has a problem with drivers as well (force feedback not working anymore). So I think that the combination Windows10 + Logitech is absolutely terrible. Whatever Logitech touches ultimately gives issues with win10 and drivers, this is my perception.

Thanks a lot I will try. As a matter of fact, I cannot get rid of HUD as it is the ONLY means I have in this moment to invert the throttle axis, otherwise I can't fly. Maybe something is wrong with HUD or hotas or both.

Bump Anyone?

Hi pilots, I've got a brand new x56 rhino to help me being more precise with my black shark. It is a great Hotas full of buttons but... It came with the throttle axis inverted. I don't know if this is a production issue or it's normal. Anyway, after a lot of troubleshooting (of course in game "invert" was not working) I found the only way of inverting the throttle to normal was to invert the axis in the HUD gaming SW. The issue is, no matter what I do, the setting is lost after I restart the pc. Tried to save the profile, but apparently the profile settings are saved only as far as key mapping is concerned; no axis tuning is saved. Unless I'm getting this terribly wrong of course. Can you support? Someone had similar issues? Thanks a lot! Max

Thanks a lot. I will try. It turned out that I had a damn mother board utility that was throttling my cpu down to 2.2 ghz. Now I'm breathing again... I will now optimise it. But yesterday I had a ramp start and a circuit just to scratch the rust and I was amazed how realistic is to fly with the rift and how easy it makes to fly, since the situation awareness is so realistic. Max

Thanks a lot guys. You are really helpful. My cpu is running indeed at 4.4 ghz oc. I managed to run smoothly (well, smooth enough so to speak) lowering all settings down. I also set vsync off in nvidia panel. So at least I can fly. I will now start from here and go up step by step. Looking forward to v2 when ed will merge. This sim in vr is simply amazing. My brain is cheated and I think I can feel the g force during the turns when I look down! By the way don't know what I did but also the judder has gone...

Guys, Seriously, no one is willing to help me? I keep on reading posts if people running smoothly dcs with oculus and gtx 980 (even 970). What do I get wrong?? It can't be that I struggle that much with a 1080. Thanks for your support!

Dear pilots I'm a ka50 and a10 user. I recently switched to oculus rift and enjoying the virtual experience but I have serious issues with fps. My rig: Windows 10 As rock extreme 4 gen 3 Intel i7 2600k 16 gb RAM ddr3 corsair vengeance Inno3d gtx 1080 founder edition I'm running dcs 1.5. The tracking is quite good, I only get some annoying judder. The problem is the fps. The fps is really low as low as 15 fps so not playable. It happens with the kamov of course because I mainly fly low level but also with a10. All I did is to push "VR" in settings. Maybe I'm missing some very important setting as I did not expect so poor performance. Some particular settings in nvidia control panel I should pay attention to? Some trick or something I don't see? It is true that the cpu is quite old and could bottleneck but I have it overclocked @4.4 ghz. The card is as well overclocked... It can't be so poor the experience... Thanks a lot for helping me. Max

Thank you. I'll see what I can do, and see if after installing 1.2.3 things will get better. m

Hi, I'm using BS2 in DCS World, v 1.2.2. I'm running it on a i7 2600 oc @4.8 GHz, with a double Crucial M4 SSD, 16 GB ram Corsair vengeance, and a crossfire of 2 HD6870. So far, so good in single player: apart from the fact that I can't get the crossfire work on BS2, I get a solid 45/55 FPS most of the time in my single player sessions. This is using a single card with crossfire off. When it comes to multi though, things get odd: sometimes I get 45 fps, sometimes (and I don't change any config or setting!!) I start at 30, but average is 20/25. WTH? I know that it depends on the mission, and also on the number of players (sorry: pilots :-) ), but it seems like a ceiling cut-off, more than poor performance, as if it was set as a maximum level. But the mission maximum fps is set to 60 or, in general, has no limits. I immediately recognize when things go smoothly, because when I enter the pit I immediately see a 45 fps, otherwise it is set to 30 and then during the mission it can only get worse. What happens? Can someone help me exploiting down to the last hertz of my rig?? Thanks, Max

thanks everybody. I got a clear idea now. will try again and finally i'll get track ir if issues persist.

Love this!!

Hi Turnburn, thanks you for your reply. So, when you say settings at startup, you mean in the Track IR software? Is there anything to be set up in the simulator? thanks, M

Hi, just a question. I'm very tired of tweaking with freetrack settings, so I'd like to move towards a really working and ultimate solution for the cockpit of my ka50. I already have a track clip pro, but I could get a 3LED hat if necessary. The question is: if I buy a Track IR 5, will I be able to get real 6DOF and a FULL zoom on every single gauge till maximum detail, also on lateral panels? I really need that, cause with freetrack is impossible. Does it affect much FPS? I'd like to know the experience of BS2+Track IR users. Thank you, M

Thanks again, will try. Let you know the results, M

Thank you falcon, I'll try out this night. As far as I remember though, I had tried it already and it it was not working. Still I have the Z axis problem, it won't work at all and is impossible to zoom at the gauges. Maybe I have to modify also the input.lua or other lua files?

Anyone, please?