Ramstein

I put some up into a zip in user files: https://www.digitalcombatsimulator.com/en/files/?set_filter=Y&arrFilter_pf%5Bfiletype%5D=70&arrFilter_pf%5Bgameversion%5D=&arrFilter_pf%5Bfilelang%5D=14&arrFilter_pf%5Baircraft%5D=&arrFilter_DATE_CREATE_1_DAYS_TO_BACK=&CREATED_BY=ramstein&sort_by_order=TIMESTAMP_X_DESC&set_filter=Filter I don't think there is a direct link smaller than this. Many profiles in here,, use what you want.

since the last update 2.5.1 auto start only starts left engine. Have to start right engine manually. Broken in last patch.

well, down low, it can be very bright in say the desert.... or snow... otherwise, up at the very high altitudes (real life), very bright... but need sun visor now! it really brighter than it was... at least it sure looks brighter...

Sun is extremely blinding, not sure about window tint, have to find tinted visors... very hard time seeing in blinding light in cockpit from the sun. Anyone else? :doh:

I see you suffer the same fate as me with the Mig-21 with every 2.5 update. And when I post about it, everyone tries to imply I am going into files and messing things up. I didn't do anything, I didn't even know how. I just spent a zillion hours trying to fix this problem again. I see you too have Saitek, maybe the problem is related to the same stick and software, that we both use? :joystick: problem is this issue will probably happen every update !!!! :helpsmilie:

I went back in again after last update, and fixed the missing code.... something erases the code or changes it during updates/patches.... Shouldn't it be locked? or some type of checksum in the process? Removing the module and re-installing doesn't fix it when it goes bad during updates, only way to fix it, it appears is to going into files and search and fix code that get's changed... I hope this is the only module that got messed up. I didn't have any problems during the patching. Only problem was the weapons not working because of the inability to assigning those bindings (Weapons release, Weapons fire), because those blocks were locked and empty.

It did it again with the latest patch (05-11-18 OpenBeta), but so far, cannot fix the problem, the weapon spaces are blank and cannot be changes... uninstalled bmig-21, re-installed, also deleted files, and it rebuilt them, but still the same problems... been at it for several hours,, had enough! Flew on server with patch Thursday night, no problems, well except for al the bugs... but did not try the mig-21 until now after latest patch on Thursday.

don't like it? turn it off.. I agree... wish I could see stuff... :joystick:

yes, it went from good to terrible.... can hardly make out what I am looking at... very bad now...

no, how could I edit it, I had no clue about the file... I remember about some forum script about 15-20 years ago.... this reminded me of that I never ever mess with these files. This is the deepest I have ever seen in these... I know what commenting out is... == {........ blah blah blah.. I don't understand how that happened... I still have to see what other aircraft are good or bad... That that I know how to fix this..., but i hope I never see it again... I spent a couple days on these problems, and still have lots to test.... I don't want to go to fly something and find out it is not working correctly... I do see OpenBeta copies some files from release version when it updates/patches, it has to be happening then..

thank you! it turned out the lines were there, but had been commented out.. a '--' was before the lines ! I have no clue how this happens! a long time I ago I remember working with some code like this, but to many years has passed and I can't think very well. I wonder how lines get commented out during a patch update? Thank you again... I still have a lot of aircraft to test... that were in the openbeta patch. The check files should catch changes like this... too look and compare changes from patches, a checksum, etc...

I uninstalled and re-installed mig-21. No fix. Must have to uninstall more files somewhere.. ! arrrghhh!!!!

Hi, every since the 2.5 patch, I am unable to assign weapons keys in the control panel. I can assign joytsick and pedals.... I can assign other controls, but not the pickle, weapons, and fire, weapons. They are just greyed out. I tried deleting some folders and files, and when they came back nothing was fixed. I am not sure if any other modules have messed up on me with this issue. I am slowly checking each module for issues after the last OpenBeta 2.5 update patch. I will attach photo.. I could not get the photo of the space for the weapon, but it is greyed out... and i had these working fine until the 2.5 ob patches...

calls to 'Scottie' in the engine room (Star Trek).... give the carrier more power Scottie, into the wind, to push my shuttle pod back using wind..... Scottie: I can't give the carrier any more Captain', she'll blow....

I ordered: Silicon Power 240GB M55 M.2 2280 SSD $70.00

Flew in many helos,, the sound is wrong, we should hear much more of the turbine and less of the blades whipping,,, the people on the outside, areas nearby will hear the blades mores... FYI.. IMHO.. I have not read the bugs lately, but hope that the underpower is reported... thanx :joystick:

a team member also who flies regularly, and has since day one with dcs also had the same problems by that farp with the Huey. There were no problems at the airfields

just on regular radio f1, f2, t3, etc..etc.. with the F10 special assignments.. and communicated I could load troops, unload, pack, unpack, etc...

Huey issues on a popular campaign server. I could not change the loadout, remove extra weight, like the rockets (default). I flew to the FARP. Right next to it a couple feet. No change in fuel or loadout. The first Huey mission, I left he loadout as it came in default, stuck with both rockets and guns and loaded troops and repair kit. I watched the exhaust gas temps and was climbing out, only taking the routes which were the lowest ranges and easiest to fly over. Engines finally failed before I could get to the target area. Crashed. If someone else is successful with this in the current release with the Huey and can make changes and not blow up, let us know. I was next to the FARP. only a few short feet and could load troops but could not change the default loadout of the fuel and weapons. I was told I did not have to be on top of the FARP. So that is why I was just next to it. I think it's bugged.... and am not going to fly it again unless the mission builders fix it, or I can figure out what is messed up. I was reading about the Huey FM in the DCS forums, and it appears there are some people who think it needs some fixing. I was not happy with the loadout being fixed with roackets and guns on the doors and not being able to change them in the server, at the FARP. I was in lots of Hueys in the USAF and went on some wild rides with roller coaster flights, with extreme G's pulls up and down and around and the engines didn't complain. I am suspicous of DCS Huey model, (Belsimtek). I feel many differences, but of course a computer and real life, way different. In real life the Heuy did not shake near as much. The performance was much better. The sound was more turbine whine. I only have the Huey, Mi-8 and Ka-50, so I cannot fly the other one in that server for the Farp missions. IMHO

the last patch has improved it all 85%

update: FIXED ! Thank You DCS ! BS is now an upstanding member of the great family! no longer an upgrade, but a full module. I created a BS2 trouble ticked because my BS2 (BS1 upgraded to BS2 many years ago) also screwed up with todays patch. It only happened with OpenBeta 2.5 patch today. Release version seems good so far. it locked me out of BS2 in Open beta after it kept complaining about my serial. They should have just upgraded us to normal instead of a bad cousin. IMHO :cry:

last time I flew, it didn't pull left.. so must have been my worn out flight stick, pedals, etc

I agree Merlin ! Something is wrong! You said it best! :joystick:

just saying what they are like in person,, I spent 3 years with these aircraft...

in DCS it may look small too you.... but the F-5 is actually about the smallest fighter... the Mirage is very big in real life. You could put an F-5 on each wing.