FSKRipper Posted June 12, 2016 Posted June 12, 2016 Hey fellow simmers, I'm a proud owner of the Bf 109 since yesterday and encountered a problem regarding the Revi. As you can see in Pic one everything looks fine when flying in 2.0. The "guncross" is always visible even with TrackIR. As shown in pic 2, I have some problems getting the cross into my line of sight and have to make the weirdest sport exercises in front of my computer. Version is 1.5.3 stable. Both Clients are up to date and the deletion of my Input Folder didn't changed anything. I have manually checked the settings in both versions and use even the same options under the special options tab. Is there a Version difference between this two or am I missing a relevant setting? 1 i9 9900K @ 5,0GHz | 1080GTX | 32GB RAM | 256GB, 512GB & 1TB Samsung SSDs | TIR5 w/ Track Clip | Virpil T-50 Stick with extension + Warthog Throttle | MFG Crosswind pedals | Gametrix 908 Jetseat [sIGPIC][/sIGPIC]
Ala13_ManOWar Posted June 13, 2016 Posted June 13, 2016 Point of view is movable and savable. You probably hit some view keys inadvertently. I don't remember what the view movement keys were, but I know F10 saved them. Look for in the handbook or here in forums, it was some Shift, Ctrl, Alt and I think enter and backspace combination or something like that. S! "I went into the British Army believing that if you want peace you must prepare for war. I believe now that if you prepare for war, you get war." -- Major-General Frederick B. Maurice
FSKRipper Posted June 13, 2016 Author Posted June 13, 2016 Point of view is movable and savable. You probably hit some view keys inadvertently. I don't remember what the view movement keys were, but I know F10 saved them. Look for in the handbook or here in forums, it was some Shift, Ctrl, Alt and I think enter and backspace combination or something like that. S! Thanks for the tip but this is not the point. In 2.0 I can move around the whole pit and can see the guncross from every position. In my 1.5.3 module there is only one position frome where I can see the guncross through the Revi. I can say for sure that I changed no viewpoints since this problem occured from the first time after I installed the module. i9 9900K @ 5,0GHz | 1080GTX | 32GB RAM | 256GB, 512GB & 1TB Samsung SSDs | TIR5 w/ Track Clip | Virpil T-50 Stick with extension + Warthog Throttle | MFG Crosswind pedals | Gametrix 908 Jetseat [sIGPIC][/sIGPIC]
Art-J Posted June 13, 2016 Posted June 13, 2016 Are You absolutely sure You've got the new "camera origin" (or whatever it's called) setting in special options set up the same in both versions? The first screen looks as if it's set to "gunsight", the second one is definitely set to "cruise", as that's the one I use in both versions (don't like my pilot suffering from scoliosis :D ), and I know this one works allright in both. i7 9700K @ stock speed, single GTX1070, 32 gigs of RAM, TH Warthog, MFG Crosswind, Win10.
FSKRipper Posted June 13, 2016 Author Posted June 13, 2016 Are You absolutely sure You've got the new "camera origin" (or whatever it's called) setting in special options set up the same in both versions? The first screen looks as if it's set to "gunsight", the second one is definitely set to "cruise", as that's the one I use in both versions (don't like my pilot suffering from scoliosis :D ), and I know this one works allright in both. Thanks Art J. I had both on Auto. It looks a bit strange because I made some movements with Track IR to get the guncross into view. After switching to cruise it looks fine at the start but as soon as I reset Track IR I get these problems again. i9 9900K @ 5,0GHz | 1080GTX | 32GB RAM | 256GB, 512GB & 1TB Samsung SSDs | TIR5 w/ Track Clip | Virpil T-50 Stick with extension + Warthog Throttle | MFG Crosswind pedals | Gametrix 908 Jetseat [sIGPIC][/sIGPIC]
RedShoes Posted June 13, 2016 Posted June 13, 2016 Jep, looks like somehow screwed up Default View to me. Try reading up http://en.wiki.eagle.ru/wiki/Snap_views especially the Customising Default view chapter. I have only the 1.5.3 version and my default view in the 109 is perfect. What every now and then gets me, is that double clicking the mouse wheel sets you in some adjust view mode. Some times when scrolling the mouse wheel to e.g. adjust some clickable cockpit item, I accidentally adjust the view and then it looks screwed up like in your pic. Usually hitting NumPad 5 puts you back to default view and it's all fine then (as long as the default view is correct in the first place). 1 Gigabyte Z370 Gaming 7 | i7-8700K | 32GB DDR4 3600 | GeForce GTX 1080 Ti FE | EKWB custom loop water cooling | Samsung M.2 EVO 960 500GB SSD + 2 x Crucial 250MX SSD + 4TB HD | Asus PG348Q 3440x1440 | TrackIR5 | Oculus Rift CV1 | MSFFB2 w extension + Saitek X52 Throttle + MFG Crosswind | Windows 10-64
Art-J Posted June 14, 2016 Posted June 14, 2016 Thanks Art J. I had both on Auto. It looks a bit strange because I made some movements with Track IR to get the guncross into view. After switching to cruise it looks fine at the start but as soon as I reset Track IR I get these problems again. I admit I haven't tried "auto", nor did I try resetting the TIR in-flight, so there might be something iffy with the way it works. 1 i7 9700K @ stock speed, single GTX1070, 32 gigs of RAM, TH Warthog, MFG Crosswind, Win10.
FSKRipper Posted June 14, 2016 Author Posted June 14, 2016 Jep, looks like somehow screwed up Default View to me. Try reading up http://en.wiki.eagle.ru/wiki/Snap_views especially the Customising Default view chapter. I have only the 1.5.3 version and my default view in the 109 is perfect. What every now and then gets me, is that double clicking the mouse wheel sets you in some adjust view mode. Some times when scrolling the mouse wheel to e.g. adjust some clickable cockpit item, I accidentally adjust the view and then it looks screwed up like in your pic. Usually hitting NumPad 5 puts you back to default view and it's all fine then (as long as the default view is correct in the first place). I admit I haven't tried "auto", nor did I try resetting the TIR in-flight, so there might be something iffy with the way it works. Thanks a lot for your time guys. As you can see below I adjusted the default view to get a chance to see the guncross through the Revi even if it means that my virtual head is bouncing on the canopy :music_whistling: I think this will be a proper solution until I get what is wrong with my 1.5.3 since even a repair changed nothing. i9 9900K @ 5,0GHz | 1080GTX | 32GB RAM | 256GB, 512GB & 1TB Samsung SSDs | TIR5 w/ Track Clip | Virpil T-50 Stick with extension + Warthog Throttle | MFG Crosswind pedals | Gametrix 908 Jetseat [sIGPIC][/sIGPIC]
Ala13_ManOWar Posted June 14, 2016 Posted June 14, 2016 That screen looks pretty correct. Second centred one is what you usually see in 109 cockpit using trackIR. I don't think it can be much better. S! "I went into the British Army believing that if you want peace you must prepare for war. I believe now that if you prepare for war, you get war." -- Major-General Frederick B. Maurice
LeCuvier Posted June 15, 2016 Posted June 15, 2016 how to switch from "cruise" to "gunsight"? Are ... the second one is definitely set to "cruise", as that's the one I use in both versions (don't like my pilot suffering from scoliosis :D ), and I know this one works allright in both. Hi Art, you say that you always use the "cruise view". That seems ok while you're just cruising. But when you enter combat you need to see the gunsight. How do you enable the gunsight from the default "cruise view"? 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
Art-J Posted June 16, 2016 Posted June 16, 2016 Hi Art, you say that you always use the "cruise view". That seems ok while you're just cruising. But when you enter combat you need to see the gunsight. How do you enable the gunsight from the default "cruise view"? Just using TrackIR to lean right a little and aim. i7 9700K @ stock speed, single GTX1070, 32 gigs of RAM, TH Warthog, MFG Crosswind, Win10.
FSKRipper Posted June 26, 2016 Author Posted June 26, 2016 The 1.5.4 open beta update solved my problem. i9 9900K @ 5,0GHz | 1080GTX | 32GB RAM | 256GB, 512GB & 1TB Samsung SSDs | TIR5 w/ Track Clip | Virpil T-50 Stick with extension + Warthog Throttle | MFG Crosswind pedals | Gametrix 908 Jetseat [sIGPIC][/sIGPIC]
Recommended Posts