[-noun] Web community dedicated to ensuring PC games run properly on your tablet, netbook, personal computer, HDTV and multi-monitor gaming rig.
https://www.wsgf.org/phpBB3/
I tried manually changing the resolution in the 'config.cfg' file but no luck.
overdriven12 wrote:there was already a fix for the FOV but yeah.. http://games.on.net/2013/11/call-of-dut ... ctivision/
mattyman wrote:Back in COD4 the command could be changed in the config file.
Does adding seta cg_fov "65" to the config file work? (Replace 65 with your desired FOV).
Command found here:
http://bashandslash.com/index.php?Itemi ... &task=view
Funkengreuven wrote:I hate to ask so soon, but is anyone working on, or considering, writing a plugin for Ghosts? I know you guys are busy, and if it wasn't for Widescreen Fixer most of us wouldn't be able to play over half the games we regularly play in surround; but I'm really looking forward to trying to get something out of this game... I hope turns out more like BO2, and less like MW3. The game in surround without a fix looks a lot like MW3 does...
valcan_s wrote:Funkengreuven wrote:I hate to ask so soon, but is anyone working on, or considering, writing a plugin for Ghosts? I know you guys are busy, and if it wasn't for Widescreen Fixer most of us wouldn't be able to play over half the games we regularly play in surround; but I'm really looking forward to trying to get something out of this game... I hope turns out more like BO2, and less like MW3. The game in surround without a fix looks a lot like MW3 does...
Yes, Dopefish is looking into it, as soon as he is done installing it he is going to try and make a fix --> http://www.wsgf.org/forums/viewtopic.ph ... start=1350
Best relax and give it some time.
Code: Select all
1>------ Rebuild All started: Project: FlawlessWidescreen, Configuration: Release x64 ------
1>Build started 11/7/2013 7:34:09 PM.
1>_PrepareForClean:
1> Deleting file "x64\Release\FlawlessWidescreen.lastbuildstate".
1>InitializeBuildStatus:
1> Creating "x64\Release\FlawlessWidescreen.unsuccessfulbuild" because "AlwaysCreate" was specified.
1>ClCompile:
1> ati_eyefinity.cpp
1> ApplicationState.cpp
1> controls.cpp
1> controls_base.cpp
1> controls_events.cpp
1> controls_properties.cpp
1> controls_subclasses.cpp
1> cpudetection.cpp
1> displaydetection.cpp
1> fasm.cpp
1> filefinder.cpp
1> GDIFontCache.cpp
1> HackTools.cpp
1>ApplicationState.cpp(1809): warning C4482: nonstandard extension used: enum 'enumComponentTypes' used in qualified name
1>ApplicationState.cpp(1813): warning C4482: nonstandard extension used: enum 'enumComponentTypes' used in qualified name
1>ApplicationState.cpp(1817): warning C4482: nonstandard extension used: enum 'enumComponentTypes' used in qualified name
1> Logger.cpp
1> LuaBinds.cxx
1> lua_includes.cpp
1> main.cpp
1> md5.cpp
1> md5wrapper.cpp
1> plugin.cpp
1> pluginmanager.cpp
1> plugin_sharedobjects.cpp
1> softth.cpp
1>HackTools.cpp(2244): warning C4355: 'this' : used in base member initializer list
1> tools.cpp
1>HackTools.cpp(3254): warning C4355: 'this' : used in base member initializer list
1>HackTools.cpp(3279): warning C4355: 'this' : used in base member initializer list
1>LuaBinds.cxx(3414): warning C4995: 'strcpy': name was marked as #pragma deprecated
1>HackTools.cpp(3570): warning C4355: 'this' : used in base member initializer list
1>HackTools.cpp(3913): warning C4355: 'this' : used in base member initializer list
1>HackTools.cpp(4670): warning C4996: '_wcslwr': This function or variable may be unsafe. Consider using _wcslwr_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details.
1> c:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include\string.h(336) : see declaration of '_wcslwr'
1> windowtools.cpp
1> Window_ConfigurationEditRepo.cpp
1> Window_LicenceAgreement.cpp
1>tools.cpp(490): warning C4995: '_tcscpy': name was marked as #pragma deprecated
1>tools.cpp(490): warning C4995: 'wcscpy': name was marked as #pragma deprecated
1>tools.cpp(490): warning C4996: 'wcscpy': This function or variable may be unsafe. Consider using wcscpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details.
1> c:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include\string.h(283) : see declaration of 'wcscpy'
1> Window_UpdateSummary.cpp
1> Window_Viewport.cpp
1> rapidxml.hpp
1> updatemanager.cpp
1> Window_About.cpp
1> Window_Configuration.cpp
1> Window_Main.cpp
1> winsockinc.cpp
1> win_registry.cpp
1> wmi.cpp
1> wmi_eventsink.cpp
1>Link:
1> Creating library C:\FlawlessWidescreen_final - Copy\x64\Release\FlawlessWidescreen.lib and object C:\FlawlessWidescreen_final - Copy\x64\Release\FlawlessWidescreen.exp
1> Generating code
1> Finished generating code
1> FlawlessWidescreen_final.vcxproj -> C:\FlawlessWidescreen_final - Copy\x64\Release\FlawlessWidescreen.exe
1>FinalizeBuildStatus:
1> Deleting file "x64\Release\FlawlessWidescreen.unsuccessfulbuild".
1> Touching "x64\Release\FlawlessWidescreen.lastbuildstate".
1>
1>Build succeeded.
1>
1>Time Elapsed 00:00:41.04
========== Rebuild All: 1 succeeded, 0 failed, 0 skipped ==========
valcan_s wrote:Thanks for the update, can you not just set your proj to the any CPU profile in vs? would of thought that profile would work and you don't need to make it explicate x64 profile and your code does not have to be modified.
HaYDeN wrote:valcan_s wrote:Thanks for the update, can you not just set your proj to the any CPU profile in vs? would of thought that profile would work and you don't need to make it explicate x64 profile and your code does not have to be modified.
In .NET you can do that because it's a heavily interpreted language, but not in C++, eg. anything pointer related wont fit in a 4byte integer, you have to use the correct type, typically size_t - that does however get defined at compile time.