Which Windows version are you using?
-
Win 7 Home Premium 32 bits
-
Win 7 HP 64bit for gaming.
For all the other things Fedora/Xubuntu/Linux Mint -
Win 7 x64 Ultimate, runs very smooth
-
Windows XP SP3
-
Dunc, why ask? Related to release builds? Note subsystem 5.01 can be forced with any VS version (with editbin or otherwise), as well as static CRT usage so XP non-broken.
-
Win 7 Home Premium 32 Bit
-
Note subsystem 5.01 can be forced with any VS version (with editbin or otherwise), as well as static CRT usage so XP non-broken.
ā¦only if you choose NOT to make use of new APIs which are available only from Vista and up. Let alone migrating away from DX9ā¦ See every link which has a blue background in the following table:
http://linuxtesting.org/compatibility/Windows_SDK_5.0_to_Windows_SDK_6.0/x86/abi_compat_report.htmlWe WANT to make use of some of the new stuff eventually. Hence we WILL break the compatibility with XP eventually. Itās not a question of āifā, only a question of āwhenā.
Oh, and to calm you down: itās not relevant for 4.33!
-
Saw most. Other by names canāt be even remotely relevant: ODBC, DHCP(v6), codec api, hardware video decoding.
As for those that could be considered possibly relevant for the project - why consider Windows-only APIs?
While e.g. SSL a pain to begin with, thereās more gain for the programmer adding new feature to be familiar with a portable API, to avoid MSFT poorly designed APIs, bug-for-bug compatibility till hell freezes over, and other reasons that you know of.There are valid reasons for fringe workloads to use, say, overlapped IO and not methods typical across whole desktop ecosystem. Are there any in this case though?
Note implication of DX9 -> DX10+ migration being at least not discounted completely in the future Make sense. Linux guerrillas deep in the country now have a partly-working DX10/11 impl though, but i digress.
Good for all, except them poor sods who have to implement, then QA 4.33 and whatever comes next. Thatās a curse really, never get to fly any, jump in pit, takeoff, then see some bug or a glitch. Abort the flight.
-
The world must be easy to understand if you can only see black or whiteā¦
-
Desktop for pit use => Windows 7 Ultimate 64 bits (High specs, good performance)=> upgrading to Windows 9 (april 2015)
Laptop for testing => Windows 8.1 (lower specs but very smooth) -
The world must be easy to understand if you can only see black or whiteā¦
In two posts, sweeping generalization a post each. Why, of all people, you?
After 2-3 weeks in the arbitrary timeframe pass, of non-flying for all programmers in the team, weāll all be happy bikeshedding the amount of rivets, just imagine all the healthy human interaction, ejecting, and otherwise that naturally occurs then.
-
In two posts, sweeping generalization a post each. Why, of all people, you?
ā¦just to make you aware that you did exactly the same thing in your post, just on a technical basis.
Donāt get me wrong, but I currently do simply not respond well to outside input/advice on what/what not to do regarding the code. Nothing personal!
And with that being said, I vanish again for the next couple of weeks/months. :mrgreen:
Cya!
-
I just switched to 8.1
I am hoping there are no compatibility issues with all my stuff.
-
win 7 64bit is the best
-
win7 64bit
-
Win 8.1 pro. Works fine, no more or less stable than xp,vista or 7 as far as BMS is concerned.
-
This Falcon sim graphics engine is 16 years oldā¦ I had the original CD in 1999 so Iām surprised it even works in Win 8.1 and without using compatibility. I installed Flanker 2.x on W8 and it looks like garbage lots of visual errorsā¦ the original Falcon sim obviously had the better graphics engineā¦
-
omgā¦
(edit)
followed by a facepalmā¦
-
7 and no real motive to upgrade at all, iām perfectly content with it.
-
Win 8.1 pro had a bit of issue with my usb stuff but thatās sorted and Every runs fine and Dandy