BHD / C4 / DFX / JO Med Fix (UPDATED 2018/02/05)
1 Attachment(s)
If you've been having issues launching the BHD / C4 / JO Med (Or any other NovaLogic med) recently, Sil and I have found a fix for it.
Download the app below. This will install a set of compatibility flags for the mission editors to help them run properly under Windows 10 1703+. It will also allow you to install fixes for DF1, DFLW and DFTFD and other games. Thanks to everyone for all the information that helped make this app possible. Download here: http://novahq.net/files.php?ID=728 |
:clap2: :clap2: :clap2: :clap2: :clap2: :clap2: :clap2: :clap2: :clap2: :clap2:
GOOD JOB! :jump: :jump: :jump: :jump: :jump: :jump: :jump: :jump: :jump: :jump: |
I did what i have read , they are on the desktop, I've run the RunMe file as administrator, but it's not working, it says he can't find the path, cause the file AppFix.sdb needs to be in the same folder as the RunMe.bat, but it is. Can you please help? I've got Windows 10 64-bit pc.
|
hmm maybe a installer should be added so it sets it to a right directory
|
1 Attachment(s)
Quote:
Quote:
Download here fred: |
Try This:
Don't Run As Admin, run normal from the desktop because I think it's already set to give you permission. I reckon it's the same as when the Steam Installer says "don't run as admin", probably because they've already applied a dll fix which will break if you do. Edit: I'm probably wrong so an alternative (and opposite) could be calling cacls to force admin rights. IE adding something like Quote:
|
Quote:
Quote:
Addendum (system path is Drive C) Also I failed to check and see if it was on the public desktop or the User Desktop:boxer: NB: Note that All Is Fine At This End... the shim went in just fine when I dumped on on my desktop after extracting it from the default Downloads folder in the user path. |
Quote:
|
I would extract in my Downloads dir to \NovaLogicMed_Fixer\ not copy to Desktop unless inside a folder.
Then try manually install either of the following ways: Powershell (shift+right click > Open Powershell window here) sdbinst.exe "AppFix.sdb" Or alternatively type CMD or Powershell in search bar > right click Run as administrator sdbinst.exe "C:\path to AppFix location\AppFix.sdb" If it works will get a UAC prompt to install and (at least for me) does not require Admin rights. |
Quote:
"The system cannot find the path specified. The file AppFix.sdb needs to be in the same folder as RunMe.bat" |
Quote:
|
Sigh.
It installs fine from my desktop. I navigate through the system controls to the "Uninstall Programs" page and it shows up there, right at the top. Immediately after installing, I attempted to open the WIQ MED, it started first time, no trouble. Closed it and tried a different MED... it failed to start. Damn it. I'll fool around with it some more later, but I will add that the batch cannot find the AppFix.sdb unless I try from my desktop. I am conviced the number of start failures is reduced, but I can't empirically claim that. And please keep in mind that I'm having other problems with my computer. I have a cheap MP3 player and a Walkman my wife got me to replace it. The Device Manager handles them both fine the first time I plug them in. The second sometimes, too. But I plug either of them in enough times, and eventually Explorer cannot see them, and the Device Manager lists them aa "Another Device," but not as a portable device or a USB drive. Windows then fails to load on reboot and I have to restore it to a "recovery point" (Wiederherstellungpunkt). This has happened several times. I suspected a Sony root kit, but not all too terribly much. I'm pretty sure that last big update borked the system somewhere. Here's the thing: I vaguely remember reinstalling my system once. The Windows 8 it came with. I've upgraded to the free Windows 10. And did I ever get around to making a recovery image for Windows 10? Indeed, I did not. I feared that meant having to go back to Win8, but I've found a page at MS Support explaining how I can reinstall Win10 with a tool they offer for download, and I'll get on that soonish, but not today. I have a paranoidish idea that all these troubles are happening to people that haven't purchased a copy of Win10. Does that sound crazy to anyone else? |
Quote:
https://s18.postimg.org/u67zr72gp/supportedmeds.png |
I actually had to reset Win10 after the Creators Update using reset within the system Settings. I was experiencing random issues however; since has been fine.
Appears Creators Update has not been kind to some users and a reset or clean install from the Media Creation Tool has fixed a lot of issues. |
windows can change your internal paths
to handle that windows use : https://msdn.microsoft.com/de-de/lib...(v=vs.85).aspx |
i download dftfdmedv193a and Dflwmedc192b .both works fine
but i like to have the med for jointops work and xtreme |
I'll try and bundle it into a small tool tomorrow if I can get a little bit of time. That should solve the "AppDb" not found.. Then this should work perfect for everything.
Sorry for the troubles. Sometimes bat files aren't the easiest to work with I guess :D Quote:
It must be named one of the exe's above. That's how the fixes are applied in the windows app fix database. |
Okay, so the DFWIQ mod comes with a MED named Xmed.exe. I changed the name of that MED to DFXmed.exe, edited my shortcuts, and...
BLAM! MED starts every time! For science's sake, I tried the Comanche 4 Consumer MED (c4medc.exe). It's a go. Test the unlocked C4 MED (c4medc6.exe): Apparently fine. The NSODLMED.exe: Failed! (First attempt only. Subsequent attempts succeeded.) WE'RE MAKING PROGRESS! Note: the NSODLMED and the NSODLMEDU are the TIO Coop consumer 2.06b and unlocked 2.05c MEDs renamed. The TIO Coop MEDs, like the TIO Coop Mod executable, have been modified to handle a much higher number of items that these mods demand. I use them everywhere. I like the way the consumer MED displays items by item.def name, not .3di name. I use unlocked MEDs pretty much only for editing respawn numbers and part animations. I tried to start the BOMed.exe: Failed. Second attempt: Success. Tried to start both the NSODLMED and the NSODLMEDU I have in the Deep Jungle mod folder (with /mod and /d flags, of course): Successful. Hmm. I like the sense of hope in DFBHD's future all this is giving me. Perhaps some future version of the tool Scott's thinking about making can have a feature allowing a user to choose a specific MED to add the compatability flags to? |
I'll add those EXE names to the fix list when I make the little tool here shortly.
|
I updated the download, it's now a small tool that helps install the fixes instead of a batch file. Seems quite a few people have issues with batch files.
If you had trouble, download the new tool from here: http://novahq.net/files.php?ID=728 |
big thanks it works excellent now
|
Quote:
|
Oh no.
The MEDs start, but the Info, Thumbnail, and Tiler tabs remain blank. No text. I'll keep trying different compatability settings, but so far, the text didn't return 'til I uninstalled the fix. |
Can you take a screenshot of what you mean?
|
9 Attachment(s)
I thought I could make a screenshot, but in the attempt to make one, new weirdness presented itself, and if I don't post a series of screenshots, you'll unlikely be able to appreciate what I'm observing...
First, I want to explain that I often start a MED by changing the display resolution to 1280×960, starting the MED, clicking the Full Screen/Windowed symbol, returning the display resolution to 1920×1080, then dragging the lower right corner of the MED window to show the entire workspace. I do this because, in full widescreen, the area in the MED where you can select and manipulate items is wider than the area that the MED can actually display them. Simply starting in widescreen and going windowed will only almost fix this, because the part of the window where items become invisible will be gone, but you CTRL+RIGHT-CLICK to center the view on something and it's way off to the right. That makes me seasick. I'd rather go through the whole resolution rigamarole. Dave Barry thinks Resolution Rigamarole is a good name for a rock band. So! Screenshots: THEN! After all the "Sturm und Drang" I went through for that, these tab bugs stopped happening and the MED seemed to be working correctly. Or maybe it'd be better said it seemed to function as usual. Anyway, is this just happening to me? |
Anyone else have the issue Baldo posted? I can't seem to replicate that on my end, although I didn't go through the whole resolution change stuff.
|
yep The MEDs start, but the Info, Thumbnail, and Tiler tabs remain blank. No text.
|
I don't think the Resolution Rigamarole (!!!WORLDWIDESCREEN TOUR 2018!!! WITH SPECIAL GUESTS DAVE BARRY AND THE ROCK BOTTOM REMAINDERS!!!) has anything to do with it. I don't know, either, though, the testing has not been conclusive on that.
I have discovered that if you remind the system about the MED's admin rights by editing the shortcut again just before attempting to start it, it mostly works. If you start the MED and the Info tab does not immediately say "No Items Selected", try again. I'm getting acceptable results this way. I also edited the shortcuts a level deeper to run the .exes as admin for all users, just for kicks, you know? Deactivated the system specific compatability mode as well, haven't really noticed any difference, good or bad. [Incoming Ramble Alert!] Maybe we're all in a special level of hell specifically for indolent NovaLogic game mappers and modders. Maybe it's just me. Maybe I've been reading too many David Wong books. I didn't mention that over the last few days, I had to reinstall Windows 10 even though I never made a back up system image (it somehow still worked), or that even though I chose the "Preserve my files" method, it still wiped everything in the C:\Program Files (x86) directory, meaning that all the files and hundreds of hours I've spent modding effectively every game (and all your mods) I ever play was gone. It's honestly the closest I've ever been to a hefty wrist-slitting, and I've been through chemotherapy, so just imagine how I felt when I realized that the program with the virtual CD-drive I was using to save wear and tear on my Mechwarrior 3 and Pirate's Moon discs was OEM to the Windows 8 this crate came with and is possibly irretrievable, and while rummaging through the hard drive looking for its installer, I came across a folder labeled Windows.old THAT HAD ALL THE C:\PROGRAM FILES (X86) STUFF IN IT THAT I THOUGHT WAS GONE FOREVER! WINDOWS 10 SAVED THAT **** FOR ME! I WASN'T GOING TO HAVE TO RE-EDIT ALL THE MECHCOMMANDER 2 'MECHS AND PILOTS! I WASN'T GOING TO HAVE TO OH-SO-PAINFULLY REPOSITION THE CHAINSAW, PMG, AND FLAMETHROWER IN THE DFWIQ MOD! ALL THOSE SIGHT TARGAS! ALL STILL THERE! [End Ramble] So I guess it's not a special level of hell. The MEDs are quirky, but they're starting, so I'm chalkin' that up in the friggin' plus column, yeah. |
Quote:
I've had similar things happen since the new year. Luckily I have Backups on external drives. Sometimes windows just moves the whole system try Looking for a windows.old folder or some other new folder on the PC - Usually drive C Also, try a drive recovery with software like RECUVA (this works on an ssd if you're quick) works real good on hdds and it's for free. |
Off topic: Bone-chilling development... either Windows' SOP did it or I should've waited a bit to run CCleaner, but I looked in the Windows.old folder and it's basically empty. If I hadn't retrieved those files when I did, it'd be too late now. Kinda wish I could've saved my Mechwarrior 3/Pirate's Moon stuff, but I don't think I lost anything too dear to lose.
I got that virtual drive program back, too, so that's settled. On topic: I think the MEDs are mostly under control now. I have a shortcut in the start menu folder for the consumer MED running my favorite mod, and I assigned it a key combination so if I press Ctrl+Shift+Alt+4, it starts. No Info/Thumbnail/Tiler tab glitches with it so far. |
Hi, if I use this tool, I only need to use it once. why I ask if I do not use the med for a while. then I have to use the tool again, or work that way
greetings fred..nl |
Thanks a lot
It fixed the 205C med on windows 10, thank you guys.
|
Hi, I do not know if anyone else has it. But sometimes the tool works and the med worsk but.sometimes it does not work
|
Quote:
|
Quote:
|
Quote:
No problems in Windows 10 Pro but! it was locked down before the Creator Update. Write permissions are still a problem but the access errors are gone with no shims needed there. In a Windows 7 VM MEds are fine except for a slight sound delay when firing |
good news
|
All times are GMT -5. The time now is 08:11 AM. |
Powered by vBulletin®